BRS Dispatch

The problem

A 400-slot roleplay server was running emergency services through a mix of chat commands and an off-the-shelf MDT that stuttered whenever the city filled up. Reports were lost when players disconnected, and dispatchers had no live view of where units were.

What we built

1. 01Designed one resource to own calls, units and records, so the data model stays consistent instead of spreading across several scripts.
2. 02Built the interface as a React NUI with proper focus and input handling, so typing a report never leaks keystrokes into the game.
3. 03Moved every state change server-side and validated it there, so a modified client cannot close calls or edit records it does not own.
4. 04Added offline report writing: reports are drafted locally and synced when the player reconnects.
5. 05Profiled the resource under a full lobby and trimmed loops and event traffic until it settled at 0.03ms idle.