ER:LC CAD

What it does

• Provides separate Responder CAD and Dispatcher CAD pages instead of mixing both workflows together.
• Imports supported live ER:LC calls and keeps incident locations on the Fall map.
• Lets responders claim their ER:LC player, update status, receive assignments, mark assigned incidents handled, and activate panic.
• Lets dispatchers create manual calls by clicking the map, update call status and priority, assign claimed responders, and mark incidents handled.
• Turns responder panic activations into critical calls in the dispatcher queue.

How to configure it

1. Configure and enable ER:LC first, including a valid ER:LC API key.
2. Open Configure → CAD and enable the feature.
3. Select Dispatcher page roles and Responder page roles. These roles control page access directly.
4. Optionally select CAD supervisor roles for configuration access. Supervisor roles do not grant responder or dispatcher page access.
5. Choose the CAD log channel, required panic alert channel, and optional unit status channel.
6. Create at least one agency, choose its type and color, and attach responder roles and dispatcher roles.
7. Choose whether to import live ER:LC calls, allow manual calls, allow responder self-dispatch, and set the default call priority.
8. Save, then open CAD from its own server-card button or use /cad to receive the page links available to your roles.

Good to know

• Discord server ownership, Administrator, and Manage Server do not bypass CAD page roles.
• A member needs a configured responder role to open Responder CAD and a configured dispatcher role to open Dispatcher CAD.
• CAD supervisor roles can manage CAD configuration but cannot open either operational page unless they also have that page role.
• The map shows incident locations only. Responder locations are intentionally not plotted.
• Discord CAD logs display member mentions without sending notification pings.
• Handled calls close the incident and release its assignments.

Common check

If something does not work, check these first: Horizon has the needed Discord permissions, the bot role is high enough, the channel still exists, and the right staff roles are selected in Configure.