Configuring Frontier Society
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
- A society must only be accessible to its corresponding business job.
- Keep job names identical to VORP job identifiers.
- Test staff and administrator roles separately.
Features to configure
- Job-gated business access
- Society and staff administration
- Business management workflow
- Role-aware permissions
Changes and restarts
When editing Lua configuration, retain the original table structure and commas. Restart rr_society 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.