Skip to content

Extension "Sneaker"

Well, this "sneaked" in here somehow. Many people were asking for a moving map, and I looked at several solutions. Nearly all took a lot of effort to get them running, if ever. Then I stumbled across Sneaker and in all fairness - that was more or less all that was needed. It looked good, and it was easy to set up. I tried to contact the developer, but unfortunately, they are quite unresponsive. So I created a fork, added all the maps and maybe will remove the major bugs in the upcoming future.

Sneaker itself provides a webserver that then connect via the Tacview Realtime protocol to your server. You need to have Tacview running on your server though, to use sneaker. As there are still some issues, please don't configure a realtime password for now.

Configuration

Adding sneaker is quite straightforward, if you looked at the above examples already:

# config/nodes.yaml
MyNode:
  # [...]
  extensions:
    Sneaker:
      cmd: '%USERPROFILE%\Documents\GitHub\sneaker\sneaker.exe'
      bind: 0.0.0.0:8080            # local listen configuration for Sneaker
      url: https://myfancyhost.com  # optional: show a different host instead of the servers external IP
  # [...]
  instances:
    DCS.dcs_serverrelease:
      # [...]
      extensions:
        Sneaker:
          enabled: true
          debug: true               # Show the Sneaker console output in the DCSSB console. Default = false
          affinity: 0,1             # Optional: old affinity
          auto_affinity:            # Optional: core affinity settings
            min_cores: 1            # Min number of cores to be used (default: 1)
            max_cores: 1            # Max number of cores to be used (default: 1)
            quality: 1              # Quality (0 = low, 1 = normal, 2 = high, default: 1)
You need to let the sneaker cmd point to wherever you've installed the sneaker.exe binary (name might vary, usually there is a version number attached to it). DCSServerBot will auto-create the config.json for sneaker (config/sneaker.json) and start / stop / monitor the sneaker process.

Tip

You can rename the Sneaker extension in your server status embed by setting a "name" in the configuration like so:

extension:
  Sneaker:
    name: MyFancyName  # Optional: default is "Sneaker"


Configuration reference

Key Type Description Example
enabled bool Whether this extension is enabled on this node. true
name str Name of the Sneaker extension in status embeds. (range: min 1) Sneaker
cmd str (required) Path to the Sneaker executable. (range: min 1) %USERPROFILE%\Documents\GitHub\sneaker\sneaker.exe
bind str (required) Local address and port Sneaker listens on. 0.0.0.0:8080
url url Public URL shown to players instead of the server IP. https://myfancyhost.com
debug bool Show the Sneaker console output in the bot log. false
auto_affinity map Core affinity assigned to the Sneaker process. min_cores: 1
max_cores: 1
quality: 1
enabled bool Enable the Sneaker extension for this instance. true
name str Name of the Sneaker extension in status embeds. (range: min 1) Sneaker
debug bool Show the Sneaker console output in the bot log. false
url url Public URL shown to players instead of the server IP. https://myfancyhost.com
affinity any Pinned CPU cores for Sneaker (deprecated). 0,1
auto_affinity map Core affinity assigned to the Sneaker process. min_cores: 1
max_cores: 1
quality: 1

node_sneaker

Key Type Description Example
auto_affinity.min_cores int Minimum number of CPU cores to assign. (range: min 1, max 1) 1
auto_affinity.max_cores int Maximum number of CPU cores to assign. (range: min 1, max 2) 1
auto_affinity.quality int Core quality to prefer (0=low, 1=normal, 2=high). (range: min 0, max 2) 1

instance_sneaker

Key Type Description Example
auto_affinity.min_cores int Minimum number of CPU cores to assign. (range: min 1, max 1) 1
auto_affinity.max_cores int Maximum number of CPU cores to assign. (range: min 1, max 2) 1
auto_affinity.quality int Core quality to prefer (0=low, 1=normal, 2=high). (range: min 0, max 2) 1