Browse docs

Exports and Shared APIs

Find the public Crime System exports by runtime context and avoid relying on internal events or diagnostic commands.

Shared APIs

ResourceUse it for
Jobs Base client exportsDocuments, radial actions, shared player interactions and tablet panels
Jobs Base server exportsDuty, employees, service features, dispatch, storage and society money
Base exportsCurrency, inventory bridges, phone/tablet providers and the Sky library

The export belongs to the resource named in its example. A shared export still uses sky_jobs_base or sky_base, even when called from a Police, Ambulance, Mechanic, Fire, Crime, DOJ or Creator integration.

Crime System exposes client and server exports for supported integrations. Call them from the correct runtime and treat every player-supplied argument as untrusted.

Read-only exports do not authorize a later mutation. State-changing server exports still require your integration to pass valid server-owned identifiers and to preserve Crime System's permission and lifecycle checks.

Integration map

Calling an export

server.lua
local profile, error_code = exports.sky_crimesystem:GetCrimeReputation(identifier)
if not profile then
    error(("Crime reputation lookup failed: %s"):format(error_code))
end
client.lua
local territories = exports.sky_crimesystem:GetTerritories()

Integration checklist

Confirm the runtime

Match client exports with client code and server exports with server code.

Read the owning contract

Check the current source signature and return shape for the installed Crime System release before shipping the integration.

Preserve server authority

Resolve player identity, permission, ownership, items, money and state on the server before any mutation.

Handle explicit failure

Do not hide a failed export behind a silent fallback. Log the operation and error code without exposing private data.

Test through a restart

Verify that the integration handles unavailable resources and reloads its cached data after Crime System starts again.

Network events, NUI callbacks, diagnostic commands and unlisted internal globals are implementation details, not public integration APIs.

Documents and restrained targets

Crime registers its configured jobs with the shared Crime interaction policy. Identity and license inspection still require a restrained nearby target; Crime's default policy does not require job duty. Zipties are enabled by default while handcuffs are not.

Jobs Creator employment jobs and independently managed Crime organizations remain different contexts. A service ID describes employment; the Boss Menu service-number page is not a gang-number system. See Service IDs and Numbers.