Browse docs

Configuration

Understand the Job Configurator, how to create a police job, feature toggles, and the safe configuration workflow.

Configuration sources

Sky Police Job uses two configuration layers:

LayerPurpose
/jobconfigJob definitions and frequently changed settings stored through Sky Jobs Base
Open files in sky_policejob/configDefaults, fallback job data, locales, and inventory assets

When Config.UseJobConfigurator is enabled (the default), saved Job Configurator values take priority over matching fallback values in config.lua. Editing a fallback value alone may therefore have no visible effect on an already configured server.

Configurator data is stored in the database through Sky Jobs Base (sky_jobs_configurator_jobs, sky_jobs_configurator_settings), not in config.lua.

Opening the Job Configurator

Run /jobconfig in-game and select Police Jobs in the selector. The command is player-only and requires the sky_jobs_base.jobconfig ACE permission, granted through Config.CommandPermissions in sky_jobs_base/config/config.lua:

sky_jobs_base/config/config.lua
Config.CommandPermissions = {
    jobconfig = { "god", "superadmin", "admin" },
    -- ...
}

See the Permissions page for the group bootstrap per framework.

Creating a police job

Add the job

Open /jobconfig, select Police Jobs, and add a new job. Enter the job name, pick the job color, and optionally enable an off-duty job.

The job name must already exist in your framework with the intended grades — the configurator stores job data, it does not create framework jobs.

Configure shop, props, and vehicles

Fill the job shop catalog (item, label, price, minimum grade), configure job props, and add garage vehicles (model, price, trunk capacity, garage type, minimum grade, fuel type, livery, colors, and extras).

Set storage and society

Configure the job storage sizes (police storage may contain weapons) and the society account used by billing and boss workflows.

Enable systems and settings

Switch to the feature toggles and settings sections and configure dispatch, restraints, evidence, jail, and the other systems (see below).

Save

Save the configuration. Changes apply live — no resource restart is needed.

Grant boss permissions

After creating a new job, run /setboss <job> <topGrade> once so the highest grade receives every boss permission.

Feature toggles

The Police Jobs section exposes these system toggles:

  • Police Tablet
  • Billing
  • Prop Placement
  • Radial Actions
  • Restraints
  • Tracking (GPS trackers and ankle monitors)
  • Evidence
  • Jail
  • Social Work
  • Impound
  • CCTV and Speed Cameras
  • Vehicle Radar

Disabling a feature does not remove its old database data. This allows a feature to be enabled again without losing saved records.

Settings sections

Frequently changed settings are grouped into configurator sections, including:

SectionWhat it controls
GeneralPrimary color and shared UI behavior
Stations / Jail / Impound / Social WorkBehavior of the creator-backed locations, sentences, and pricing
DispatchDispatch notifications and behavior
RestraintsCuffs, zipties, leg cuffs, head bags, and escort behavior
EvidenceField kits, storage, and laboratory behavior
Devices / Speed Camera AppCCTV cameras, speed cameras, and the tablet speed camera app
TrackingGPS tracker and ankle monitor behavior
Vehicle RadarPatrol vehicle radar behavior
BillingBilling prices and offence handling
Equipment / Spike Strips / Radial ActionsDeployables and radial menu actions
Tablet AppsWhich tablet applications are available

Interactions (markers, blips, NPCs, and animations of the placed points) are edited in the configurator as well.

Stations, jails, social work, and impounds

Stations, jails, social work zones, and impound lots are creator-backed sections inside the configurator: entries are created, placed in the world, and edited from /jobconfig. The standalone commands (/stationcreator, /jailcreator, /socialworkcreator, /impoundcreator) are only available when Config.UseJobConfigurator is disabled.

See Station Setup for the placement workflow.

  1. Enable or disable the main systems in /jobconfig.
  2. Configure police jobs, shops, vehicles, dispatch, restraints, evidence, jail, and impound settings.
  3. Save the configuration and test it without restarting the resource.
  4. Use the open configuration files only for settings that are not exposed in the configurator.
  5. Keep a backup of customized configuration files before every resource update.

Open configuration files

FileUse
config/config.luaFeature defaults, fallback jobs, command permissions, and interactions
config/locales/*.luaTranslations and interface text
config/inventoryIncluded police item images

Settings that need extra care

Job Configurator police jobs

Police jobs created only through /jobconfig receive the same tablet applications as jobs defined in config.lua. After adding or changing a job, save the Job Configurator entry and ensure the player has the correct job and duty state before checking the tablet.

Command permissions

Changes to Config.CommandPermissions (in sky_jobs_base or sky_policejob) require a resource restart, and players may need to reconnect.

Evidence metadata

Evidence samples require a metadata-capable inventory. Without item metadata, collected evidence items lose their sample data — this is an inventory requirement, not a configurator setting.