Browse docs
Configuration
Job Configurator and open files
Config.UseJobConfigurator = true enables the shared Job Configurator integration. Use /jobconfig for registered jobs, interactions, settings and feature toggles. Saved configurator values take precedence over the shipped defaults.
The open files remain useful for installation defaults and settings that are not exposed in a form:
Location inside sky_dojjob | Purpose |
|---|---|
config/config.lua | Jobs, access settings, feature defaults and module configuration |
config/registry.lua | License-register selection, registry access overrides and legacy catalog |
config/registry/ | Per-register fields, certificate assignment and separate client/server hooks |
config/locales/ | User-facing resource translations |
config/style.css | Exposed resource styling |
config/img/ | Resource image assets |
import.sql | Manual database installation and upgrade statements |
Changing a fallback value does not erase a saved configurator override. To intentionally import the local resource configuration into the live configurator, use /jobconfigimport sky_dojjob. Review your saved job settings before importing.
Jobs and duty
The shipped job is named doj and uses society_doj. Configure the actual job, grades and society account used by your framework. Job entries also hold storage, lockers, shop items, vehicles and printers.
Config.Tablet.requireDuty defaults to true. DOJ tablet access therefore requires an on-duty player. The optional off-duty job is disabled in the default job entry. Job names and duty behavior must agree with your shared Jobs Base setup.
Case-file access
In Case-file access, configure:
- Prosecution grade keys: technical grade names that act as prosecution.
- Judiciary grade keys: technical grade names that act as judiciary.
- Court administration grade keys: technical grade names for administrative staff.
Choose the actual grades from the framework catalog and save your assignments. The configurator updates the internal mapping version automatically; there is no separate publication step. The corresponding file settings are Config.RecordsAuthorization.mappingVersion and Config.RecordsAuthorization.gradeBindings. Never map one grade to two domains. See Permissions for the plaintext fallback and additional action permissions.
Config.CourtWarrants.templateCodes defaults to HB, DB and RB. These identify the signed and shared warrant templates used by the Police integration. Align this list with your actual templates if you change their codes.
Modules
The following keys live in Config.ToggleFeatures:
| Key | Shipped default | Controls |
|---|---|---|
tablet | Enabled | DOJ records and tablet integration |
handovers | Enabled | Task and responsibility handovers, judicial decisions and execution reports |
bodycamRequests | Enabled | Requests for police footage; requires handovers |
legalCodes | Enabled | Legal Codes and law-book workflows |
offences | Enabled | Fine Catalogue |
hearings | Enabled | Hearing management |
courtroom | Enabled | Configured courtroom workflows |
conditions | Enabled | Structured court conditions |
publicDisplays | Enabled | Public display integration |
elections | Enabled | Elections |
printers | Enabled | Physical document printing |
civilRegistries | Enabled | File-based registers and configured legacy registry workflows |
finance | Enabled | Faction accounts and financial administration |
taxes | Disabled | Optional asset-tax collection |
Changing a shipped default does not disable a module that already has a saved enabled override. Review the live setting when upgrading an existing server.
Choose modules for your server's workflow in /jobconfig → Department of Justice Jobs → Features. Folders, workspaces, documents, case assignment and manual document sharing do not require Handovers. A DOJ case does not require a Police case, a hearing, an invoice or a jail action.
Handovers and Bodycam requests retain their previous enabled behavior when the new keys are absent from an older configuration. Disabling either workflow hides its entry points and rejects its server actions without deleting saved cases, requests, signatures or document shares. Re-enabling it makes the saved requests available again. Disabling Bodycam requests does not disable Gallery or saved recordings. Disabling Handovers also disables its Bodycam request workflow, but does not change the saved Bodycam requests preference.
Update DOJ, Police and Jobs Base together when adding these controls. Jobs Base supplies the configurator labels; Police uses DOJ's effective availability for its Bodycam requests entry. Existing permissions and saved overrides continue to apply. No database conversion or record reset is needed for these switches.
Disabling registries hides those workflows without deleting their records or disabling Citizens, Vehicles or the criminal-justice workspace. Configure separate license folders and register access through Registries and certificates. Configure treasury accounts, bank fines and provider-dependent actions through Finance.
Courthouse locations and interactions
Create the courthouse and its interactions through the existing creator tools. Config.CourthouseCreator.stationBlip controls the courthouse map blip. Config.Interactions contains the shipped appearance profiles; location and behavior belong to the corresponding creator entries. Appearance settings alone do not place a courthouse, courtroom or printer. Fresh defaults have no configured courtrooms or job-printer positions.
Printers and supplies
Each job's printers list starts empty. Configure a physical printer and its position before using Print. The default DOJ printerSettings has paper consumption disabled, a capacity of 100, refill item printer_paper and refill amount 25. Shared queue and ink defaults come from sky_jobs_base/config/printers.lua; per-job overrides are available where configured.
See Sharing and printing for the complete collection workflow and Inventory items for supplies.