These role-specific systems coordinate emergency support and temporary road control. This guide remains a draft while the two-client panic, spike-crossing, and toll walkthroughs remain unverified.
Request panic or backup support
Eligible on-duty emergency-service members can use /panic. Eligible police roles can use /backup for their own organization or an eligible organization tag supplied with the request.
These actions create an incident and notify authorized responders; they do not automatically establish guilt, force another player’s response, or replace ordinary radio communication.
Use /respond for a current activation. It records the response and attempts to provide a scene marker. Use /cancelpanic to end your own activation or, with appropriate authority, another current activation.
Duty, membership, health, character, and connection changes can end or detach active state. Panic incident records persist, but active requests and response markers do not survive restart.
Deploy temporary road controls
Authorized on-duty members use /roadblock for a supported barrier, police barrier, cone, or spike preview. Save only after reviewing the position. The adjust and remove actions manage a nearby organization deployment; /cone and /spike provide current direct surfaces.
Roadblocks are temporary runtime objects and clear on restart. An editing session belongs to the character and organization that opened it and is cancelled if duty, membership, the character, or life is lost, so save while still authorized. Adjust and remove act only on a deployment in your own world and interior. A spike strip flattens only the wheels that actually cross it and is spent by the first crossing that catches one; a vehicle that misses the strip damages nothing and leaves it armed. That behaviour has been reworked and not yet re-verified in game, so the deployment flow remains unavailable for publication.
Use or manage toll incidents
A driver uses /toll at the nearby lane to pay or claim authorized passage. Eligible public-service roles can receive policy-based passage.
Authorized members use /tolls to list sites, apply a bounded closure, declare an emergency closure, release a site, or record a justified bypass. Toll payments, passage events, and closures are durable and audited; temporary barrier-open state resets through shutdown.
Multi-site lock and release each apply as one durable result. The required real-client verification remains incomplete, so authorized closure management remains held.
Recover from unclear state
- Panic or backup is refused: confirm current duty, faction, rank access, and character state.
- A response marker conflicts: use displayed scene information rather than repeatedly responding.
- Cancellation or detach is unclear: reopen the relevant active state before issuing another request.
- Roadblock flow is unverified: do not rely on placement, adjustment, removal, or a spike crossing until the in-game re-verification is done.
- Toll closure or release is unclear: refresh the site list and do not repeat the mutation blindly.
- Restart occurs: active panic markers and roadblocks clear; durable toll closure policy reloads.
Placement limits, exact ranges and strip geometry, closure durations, fees, tactical usage, monitoring, and internal authorization identifiers are intentionally omitted.