/createbusiness. A boss then lays out the venue in-game with /setupbusiness. Both run through a tablet-style React UI, and every change is validated and persisted server-side.
Register a business — /createbusiness
/createbusiness is admin-gated. The server only honours it for players with the nex_businesses.admin ACE (or the command ACE). Admins get this shortcut for registration only — everything else is gated purely by job and manager grade.
The command links a pre-existing framework job to a new business shell, then launches the setup tool so you can start placing points.
Once the business is registered, admins have no special access to its placement or management. From then on, only a player clocked into that job with a manager grade can run
/setupbusiness and /managebusiness.Lay out the venue — /setupbusiness
/setupbusiness opens the placement tool for a boss who is on the job with a manager grade. You drop, edit, and delete every interaction point that makes a business work. Each point is placed at your feet (or via the optional gizmo) and saved immediately.
Point types
| Point | What it does |
|---|---|
| Zone | The business boundary. Defines where employees see station indicators and where /managebusiness and the dispatch widget apply. Walk the perimeter to place it. |
| Station | A prep station where employees craft menu items. Items are assigned to stations from the management dashboard. |
| Crafting | A crafting spot tied to recipes. |
| Stash | An ox_inventory stash for storing ingredients and stock. Configurable slots and weight. |
| Tray | A handover tray (slots and weight) for passing items across the counter. |
| Register | A till for ringing up sales. Can be disabled server-wide via Config.DisabledRegisters. |
| Order counter | The customer-facing point where customers place and pay for orders. Has a configurable handover distance. |
| Queue terminal | The back-of-house point where employees view and work the pending order queue. Keeps the kitchen off the customer counter. |
| Chair | A sittable chair. Uses the built-in chair system (Config.useChairs). |
| Manager menu | The zone that opens the management dashboard for managers. |
| Offline shopkeeper ped | A ped that sells the business’s stock when nobody is on shift. Configurable model, scenario, stash size, and interaction distance. |
The order counter and queue terminal are the two vectors behind the order system: customers interact with the order counter, employees work the queue at the terminal. See Orders.
Placing and editing points
- Stand where you want a point and pick it from the setup tool. Most points anchor to your feet; the offline shop ped anchors to the floor and faces the way you do.
- To reposition an existing point, use Move here (re-anchors it to where you’re standing) or the gizmo if
object_gizmois running. - Deleting a point tears down its live target / blip / stash immediately and removes it from the database.
The zone and the manager menu are singletons — placing a new one replaces the existing point for that business. Most other point types can be placed multiple times.
Optional fine placement with object_gizmo
Ifobject_gizmo is installed and running, the setup tool exposes a movable gizmo handle for precise placement instead of dropping a point at your feet. The zone is always walked manually; every other point type supports the gizmo. The resource works fine without object_gizmo — it just falls back to feet-anchored placement.
Verifying a setup
SetConfig.debugConfig = true in cfg.lua to have the script log whether a business is missing required points. This is the quickest way to catch a half-finished layout.
Next steps
- Management dashboard — once the venue is laid out, build the menu, recipes, and stock.
- Orders — how customers order at the counter and employees fulfil from the queue.