Apiary Emergency Dispatch: Multi-Incident Triage (2D)

Dispatch Console

🚨 Incidents (fire, pesticide drift, disease, theft, storm) flare up at random yards across the map. Each one bleeds hives away the longer it waits. Click an active incident (or its row below) to send your nearest free team — you can't cover everyone at once.

Active incidents

Teams free

0 / 0

Hives saved

Hives lost

Resolved

Avg. delay

— s

Incidents

No active incidents yet.

Controls

Response teams 3

Incident frequency med

Team travel speed 3

How it works

Nine hive yards sit on the map around one dispatch base. At random intervals an incident (fire, pesticide drift, a disease outbreak, theft, or a storm front) breaks out at an idle yard with a starting hive count at risk. For the first few seconds a yard is in its grace window — nothing is lost yet, mirroring the real detection-and-decision lag before anyone can act. After that, hives are lost on a clock that speeds up the longer the incident runs unattended, so a queue of ignored incidents gets worse, not just stalled.

Sending a team is a triage decision, not automatic: you choose which incident gets your next free team based on its remaining hives, how fast it's decaying, and how far your nearest team has to travel. A team that arrives in time contains whatever hives are still standing — they count as saved — but the travel time itself is lost ground the decay clock keeps ticking through.

Auto-triage runs a simple rule for comparison: always send the nearest free team to whichever active incident will lose its next hive soonest. Toggle it to see how a fixed rule compares with your own judgement calls under the same incident load.

Response teams — how many incidents you can work in parallel.
Incident frequency — how often new incidents break out.
Team travel speed — how quickly a dispatched team crosses the map.

Quiet yard Active incident Team en route / working Hives lost