Browse docs
Radial and Player Interactions
Open the radial
The shared job radial uses G by default. Configure Config.JobRadial in Jobs Base or its matching /jobconfig settings. Saved configurator settings take precedence over file defaults.
| Setting | Purpose |
|---|---|
enabled | Enable Sky's radial interface |
mode | toggle to open/close with a press, or hold to select when releasing |
logo | Optional center logo; empty hides it |
submenuOpenDelayMs | Hold-mode submenu delay; default 350 ms |
keybinds.enabled | Enable the shared direct action keybinds independently |
oxTarget.enabled | Add eligible actions to the configured ox/qb target provider |
Disabling the radial UI does not disable direct action exports or every keybind. Target-based tablet access uses the tablet item's normal usable-item flow.
Player target context
Config.JobRadial.targetContext resolves the person near the camera's look direction. An exact hit on the character's body is not required.
| Setting | Default | Purpose |
|---|---|---|
enabled | true | Resolve camera context for Sky and external radial integrations |
maxDistance | 3.0 | Maximum context-selection distance |
playerToleranceRadius | 1.1 | Radius around the look line |
playerToleranceAngleDegrees | 24.0 | Allowed angle around the look direction |
playerToleranceCloseRangeSlack | 0.45 | Tolerance for a person very close to the camera origin |
marker.enabled | true | Show the selected-person marker while Sky's radial is open |
Selection tolerance does not increase an action's allowed server distance. Individual actions still check access, proximity, target state, items and the relevant policy.
Restrain, then inspect
- Approach the person and use the authorized handcuff or ziptie action.
- Once restrained, open Player interactions → Documents.
- Inspect the person's identity, licenses or service ID, when permitted and enabled.
A hands-up visitor and an officer directly behind them produce the rear-restraint workflow shown in the showcase. Standing behind someone and hands-up are not universal requirements for every handcuff action; the server chooses the applicable interaction from the actual positions and configured rules. Ziptie policy can require hands-up.
Document inspection reads a restrained person's data directly. It does not send the earlier identity-request/consent prompt. Showing your own document to someone is a separate presentation action.
Police, Crime and Creator jobs
Config.JobPlayerInteractions.groups defines the shared policies. Police requires duty by default; Crime does not. Both default policies allow identity/license inspection, subject to the restrained-target requirement. Crime enables zipties rather than handcuffs by default.
Police and Crime register their configured jobs automatically and refresh their registration when Job Configurator settings change. Other integrations must register their owned job list through the server whitelist API. Menu visibility never grants server access.