Browse docs
Service IDs and Numbers
Service IDs
The service document shows the holder's actual employment department, rank and service number.
It is unavailable for unemployed characters. Inspecting another player's service ID uses the
existing identity permission, distance and character checks. External native ID providers
are not used for this document type.
Configure default styles in PlayerIdentityCard.serviceCards, also available in /jobconfig.
An exact job entry takes priority over *.
| Field | Values |
|---|---|
job | Employment job name, or * for the fallback. |
template | official, medical (photo on the right), or compact. |
background | matte (matte paper, default), engraved (wave pattern) or tinted (stronger department colour). Independent of the field layout. |
color | Six-digit hex accent and background colour, such as #3177b7. |
title | Optional department name; empty uses the registered job label. |
logo | Optional local filename inside config/documents. |
prefix | Up to 12 ASCII letters, digits, spaces, hyphens or underscores. An empty default uses the job name. |
format | {prefix}-{number}, {prefix} {number}, {prefix}{number} or {number}. |
digits | Minimum number of digits, 1–8; default 3. Longer numbers are never truncated. |
Tablet → Boss Menu → Service numbers lets department management change only the
prefix, number format and minimum digit count. Card templates, colours, logos and department
titles remain controlled by Config / Job Configurator. Extra management payload fields
cannot override these styles; stored presentation overrides are ignored.
This uses Manage members / MANAGE_MEMBERS
(permission 3) and the caller's current employment management context. A client-supplied
job name cannot select another department; alternate gang contexts do not manage employment cards.
Saved Boss Menu number settings override only that department's number-format defaults. Concurrent edits reject stale revisions. Reopen the page to load the latest settings; reopen a service card to display the changed number format.
Number persistence and installation
Numbers are assigned automatically on first service-card use and stored per character and job, not player server ID. Reconnecting and leaving/rejoining the same job preserve the number. Changing the prefix or format changes its presentation while retaining the underlying number. Renaming the internal job key creates a different number scope.
Managers can assign or change a member's number on the same page, including offline members. Enter only the numeric part; the department format is applied automatically. Numbers must be integers from 1 to 99999999 and unique within the department. Stale member edits are rejected; reassigning a number frees its previous value. Membership and number updates refresh open management views while preserving draft input.
Creator employment jobs use the same management, roster and allocation owner. An exact job
entry takes priority over *, whose fallback also covers newly created job names. Document
inspection retains the Creator profile's document grants and the restrained-target requirement.
Install the new sky_jobs_service_card_settings and sky_jobs_service_numbers tables.
The automatic migration creates them when AutoExecuteQuery is enabled. Otherwise run
their CREATE TABLE statements from the update's import.sql.
Atomic number allocation requires oxmysql, through the existing Jobs Base database facade.
Concurrent requests for the same character can leave harmless gaps. Allocation does not overwrite existing member numbers.
Photos remain client-local and are never stored in these tables.
Identity and licenses use the same placement, optional branding, local portrait and dismissal behavior.