Skip to content
Meridian Docs

Integrations overview

Other resources on the game server can read the radio system, react to it and control it:

  • The player-side API (client exports and events) covers one player’s own radio, for HUDs, animations and similar scripts.
  • The server-side API (server exports and events) covers the whole radio system: every connected radio, calls and emergencies, plus dispatch actions such as acknowledging emergencies, alert tones and moving radios to a talkgroup. It suits CAD/MDT resources, panic blips and duty scripts.
  • The web API (REST, a live event stream and webhooks) offers the same system view and dispatch actions to software outside the game server: web CAD/MDT systems, Discord bots, dashboards. It’s available on plans that include it.

The examples assume the resource folder is named meridian. If you renamed it, use your name in exports.<name> and in the event names (<name>:talkgroupChanged and so on).