Admin Commands Reference

Permissions

All builder commands require admin permission. Add this line to your server.cfg to give your admin group access:

add_ace group.admin admin allow

Standard QBCore/QBX/ESX admins pass the check automatically. Without admin permission, the commands respond with a "no permission" message.

Command List

Office Creation

/mowerlocation <name>

Starts an office setup using your current player position and heading.

Saved fields:

• name
• coords
• heading

This does not finish the office until /mowervehicle is used.

/mowervehicle

Captures your current position and heading as the office vehicle spawn and saves the office to the in-memory builder session.

Saved field:

• vehicleSpawn

Yard Creation

/moweryard <name>

Starts a new yard and opens the visual editor.

The session stores:

• name
• coords
• patches
• obstacles

/mowerpatch

Opens a grass model picker dialog and adds one patch at your current location.

This uses the active Config.GrassProps list for validation.

/mowerundo

Removes the most recently added patch from the yard you are building. It is meant for patches placed with /mowerpatch — while the visual editor is open, use the editor's own undo (Ctrl+Z or Backspace) instead so the on-screen preview stays in sync.

/mowerfinishyard

Saves the active yard if it has at least one patch, closes the editor, and stores the yard in the current builder session.

The yard tier is determined from patch count at save time.

Session Commands

/mowerimport

Loads the offices and yards currently live on the server into your builder session. Anything already in the session with the same name is left untouched.

Run this first if you want to review, remove, or build on top of the existing data.

/mowerlist

Prints current session contents in chat, including:

• location names
• yard names
• patch count
• obstacle count
• calculated tier

/mowerremoveyard <name>

Removes a yard from the builder session. The name must match exactly, including capitalization.

This only changes your builder session — to remove a yard from the live game, export afterwards and update shared/config/locations.lua with the result.

Export Behavior

/mowerexport

The export command does the following:

1. saves any office you are still in the middle of creating
2. saves any yard you are still building, as long as it has at least one patch
3. pulls in the offices and yards already live on the server, so nothing existing gets lost
4. writes everything to a file called exported_locations.lua inside the resource folder
5. confirms in chat how many offices and yards were exported

Important notes:

• entries are matched by name — if a session entry and an existing entry share a name, the session entry is kept
• exporting does not change anything on the live server by itself; see "Applying your export" below

Applying your export

The game keeps using the yards in shared/config/locations.lua until you update that file. To make your exported yards live:

1. Open exported_locations.lua (in the oxide-landscapingjob folder on your server).
2. Copy its contents over the matching tables in shared/config/locations.lua.
3. Restart the resource.

/mowercancel

Clears any in-progress office or yard setup for the calling admin, closes the visual editor, and removes preview state.

Visual Yard Editor

The visual editor opens automatically through /moweryard.

Modes

• patch mode
• obstacle mode

Switch modes with Tab.

Placement Controls

Precision Controls

Recommended Workflow

Builder Design Tips

• Keep office vehicle spawns clear and accessible.
• Use natural patch spacing instead of rigid grids.
• Add only enough obstacles to create interaction, not clutter.
• Test mower access paths before treating a yard as finished.
• Keep exact yard names consistent if you rely on export deduplication by name.

Next Steps