Sneaker is a browser-based radar and GCI simulation designed for use with Tacview and DCS: World. Users are presented with a simulated radar scope that provides air, sea and optionally land targets with speed/altitude/type information. Additionally Sneaker provides some GCI-specific functionality:
- Configure per-aircraft or profile based threat and warning radius's that provide visual and auditory cues for trespasses.
- Searching, tagging, and watching flights allows you to reduce workload and allow a controller to work across many flights and packages.
- Mission clock and hack timers for command and coordination.
A live example of Sneaker can be viewed here.
- Real-time track display with consistent random 5-digit IDs
- Configurable track naming (ID only or ID with aircraft type)
- Coalition-based color coding (blue for enemy, red for friendly)
- Track history trails
- Speed and altitude display
- Threat and warning radius circles
- Entity tagging system
- Discord integration for GCI coordination
- Multiple map support (Caucasus, Syria, Persian Gulf, Marianas)
Sneaker now uses a consistent random 5-digit ID system for track identification instead of aircraft types. This provides several benefits:
- Consistent Identification: Each track gets a unique 5-digit ID that persists throughout the session
- Reduced Clutter: Track names are shorter and more readable
- Privacy: Aircraft types can be hidden for training scenarios
- Flexibility: Users can choose to show or hide aircraft type information
- ID Only:
12345(when aircraft type display is disabled) - ID with Aircraft Type:
12345 (F/A-18C)(when aircraft type display is enabled) - With Pilot Name:
PilotName 12345 (F/A-18C)(when pilot information is available) - With NATO Name:
Hornet 12345 (F/A-18C)(when NATO names are available)
In the Settings panel, you can toggle "Show aircraft type in track names" to control whether aircraft types are displayed in parentheses after the track ID.
- Download the latest released version from here.
- Create a configuration file based off the example, replacing the required information (and optionally adding multiple servers to the array)
- Run the executable with the configuration path:
sneaker-server.exe --config config.json
Sneaker features a built-in Discord integration which provides basic server information and GCI duty tracking via Discord slash-commands.
- Create a new Discord Application and configure the
Interactions Endpoint URLto point at your Sneaker installations/api/discord/interactionsendpoint. - Add a Bot to the application (this is used to DM users about GCI duty timeouts)
- Add the bot to your server by opening a link generated here. You only need the
applications.commandsscope. - Add the following to your
config.json:
"discord": {
"application_id": "<discord application id, bunch of numbers>",
"application_key": "<discord public key, bunch of letters/numbers>",
"token": "<discord bot token>",
"state_path": "<optional path to a location to save GCI duty state between restarts>",
"timeout": "<number of minutes before gci is automatically logged off duty, default = 60>",
"reminder": "<number of minutes before timeout to warn gci via discord, default = 5>"
}- API provides information on the internal Sneaker API.
The Sneaker web UI presents an emulated radar scope over top a Open Street Map rendered via maptalks. The web UI is updated at a configurable simulated refresh rate (by default 5 seconds).
Bullseye information for the current cursor position is displayed in the bottom right corner of the screen, additionally the bullseye icon is rendered in its position on the map.
A BRAA line can be drawn by right clicking anywhere on the map and dragging. Additionally if you press the "s" (snap) key while starting the BRAA line on-top of an existing track the starting point will be locked to the tracks position.
The mission timer is available in the bottom left corner. Clicking on the timer will create a new hack timer which will display above.