Configuring Frontier Dispatch
Keep your server settings, identifiers and dependencies consistent.
Configuration location
The commonly used configuration path for this resource is config.lua. Verify the path against the release you downloaded; some versions organise shared or client/server settings differently.
Recommended checks
- Start
rr_blackmarketbefore dispatch if your version requires it. - Check job restrictions before exposing sensitive robbery alerts.
- Verify waypoint integration using a live test robbery.
Features to configure
- Notifications for configured robbery events
- Police-directed incident information
- Dispatch ledger and incident tracking
- Waypoint and navigation handoff
Changes and restarts
When editing Lua configuration, retain the original table structure and commas. Restart rr_dispatch after saving and retest relevant interactions. If a field references an item, make sure the item exists in your VORP inventory database. Do not publish Discord webhooks, secret credentials or private server identifiers in public documentation.
Need an exact field-by-field reference? Use the resource's bundled
config.luaand README. Only configuration details verified from a specific release should be copied into a customer-facing example.