Authorized Fire/EMS members can discover active fire incidents, inspect their progress, and suppress them with finite organization equipment. This guide remains a draft until the interior walkthrough, the two-client scene on a real client, and sustained-load testing are complete.
Prepare for a response
Before responding:
- Enter organization duty at an owning armory.
- Issue an authorized fire extinguisher and its charge from organization stock.
- Unpack the extinguisher and load the issued charge into it. An extinguisher is issued empty, so this step is what makes it usable, and it is also how you refill one you have run down.
- Confirm the extinguisher remains assigned to your character and ready to use.
- Review the dispatch board for scene information and attach through the ordinary responder workflow when appropriate.
Duty alone does not issue equipment or create unlimited extinguisher charge. The physical extinguisher and its remaining charge stay accountable to the organization.
Find the active incident
Use /fires to list active incidents while on duty with fire-response authority. The list provides temporary fire references, location, remaining intensity, and time remaining. Reopen it after a scene changes or a reference is refused.
Use /firestatus with a listed reference to review one incident. At the scene, the command can instead resolve a nearby unambiguous fire in the same exterior or entrance context. The status includes active nodes, remaining intensity, dispatch state, and bounded response totals.
A 911 report requesting the fire service creates a dispatch call, not a mechanical fire by itself. Follow the dispatch description until an authorized incident appears on the fire list.
Suppress the fire
At the scene:
- Leave the vehicle and make sure your character is conscious, unrestrained, and able to act.
- Equip the exact assigned extinguisher, already loaded with charge.
- Move into the same exterior or entrance context as the fire.
- Aim directly at a visible active flame and use the extinguisher normally.
- Watch the bounded progress feedback and recheck
/firestatusas needed.
Accepted spray consumes durable extinguisher charge and lowers one fire node. Spraying from the wrong context, through an obstruction, out of useful range, without authority, or without charge has no suppression effect. Multiple responders may work the same incident; the server records only accepted contributions.
Fire causes real environmental harm. Firefighters do not receive scripted immunity, so keep distance where the scene allows and coordinate treatment for injured characters.
Understand the outcome
An incident is successfully extinguished only when all of its active nodes reach zero. Uncontrolled fires eventually burn out, and staff may cancel an invalid or ended scene. Burnout and cancellation are not responder successes and do not grant rewards.
The mechanically linked dispatch call closes through the fire incident’s outcome. Responders cannot independently clear that producer-controlled call.
Recover from a refusal
- No incidents appear: confirm duty and rank authority, then check the dispatch board. A caller report may exist without a mechanical incident.
- A fire reference is refused: reopen
/fires; references are temporary and scoped to that list. - Nearby status is ambiguous or absent: use
/firesand select the intended reference instead of repeatedly using automatic resolution. - Spray has no effect: check duty, assignment, loaded charge, held weapon, scene context, distance, and a clear aim at an active flame.
- Equipment or incident evidence is held for review: stop spraying and preserve the displayed message. Do not discard, transfer, or replace the assigned extinguisher to work around it.
- Reconnect during a response: re-enter duty if needed, verify the assigned equipment state, reopen
/fires, and inspect the incident again before spraying.
For issuing and returning service equipment, continue to Going on duty and selecting a service uniform. For call attachment and scene routing, see Calling 911 and emergency dispatch.
