Oxide Landscaping
Landscaping job system for FiveM servers.
Oxide Landscaping is a landscaping job resource for FiveM servers built around office-based shifts, progression, crews, yard mowing, obstacle cleanup, and in-game yard-building tools.
Current Highlights
- Shift-based job flow with office clock-in, assigned yards, and end-of-shift payout
- o-link integration for callbacks, notifications, phone/email delivery, targets, menus, clothing, fuel, keys, and player lifecycle events
- Vue NUI manager flow with
o-linkmenu fallback - Unified
job_progressionstorage for landscaping progression data - Optional uniforms, crew co-op, floating yard waypoints, and optional
xsoundmower audio - In-game builder tooling for office creation, yard creation, import/export, and visual patch/obstacle placement
Requirements
| Resource | Required | Purpose |
|---|---|---|
ox_lib | Yes | Locale support, shared helpers, and UI utility usage |
oxmysql | Yes | Database access |
o-link | Yes | Integration layer used by this job |
xsound | No | 3D mower audio |
Quick Start
- Place
oxide-landscapingjobin your server resources. - Ensure dependencies first in
server.cfg. - Import
sql/install.sql. - Run the optional migration if you still use older per-job progression tables.
- Review the
shared/config/...files and start the resource.
ensure ox_lib
ensure oxmysql
ensure o-link
ensure xsound
ensure oxide-landscapingjob
What Changed
The current landscaping job uses o-link as its integration layer and stores progression in the unified job_progression table with job = 'landscaping'.
Behavior now documented on this site includes:
Config.menuStylefor NUI vs menu fallbackConfig.shiftSummaryfor text vs NUI end-of-shift summaries- phone/email delivery through
olink.phone.SendEmail(...) - bank payout behavior with cash-based destruction fines
- builder export behavior centered around
exported_locations.lua