Configuration
The plugin's config is deliberately tiny. There are only two settings — your key, and the backend URL you leave as-is. Everything else is fixed.
The full config
After the first start, plugins/WardenAC/config.yml looks exactly like this:
plugins/WardenAC/config.yml
# ── Warden AC ──
# Your network key from the dashboard (Settings). Required.
server-key: "wrdn_live_xxxxxxxxxxxxxxxxxxxxxxxx"
# Backend connection (leave as-is).
backend-url: "wss://backend.wardenac.com/bridge"Options
| Option | What it does |
|---|---|
| server-key | Your network key from the dashboard (wrdn_live_…). The same key goes on every server in your network. This is the only value you need to set. |
| backend-url | The backend the plugin connects to. Leave it as wss://backend.wardenac.com/bridge — you should never need to change this. |
What about sampling rates?
Older setups had knobs for the snapshot rate and the live-map sampling (radius, step, interval). Those are now fixed in the plugin at sensible values so every network behaves the same and stays light on both your servers and ours. There's nothing to tune — it just works.
The server identity file
On first connect, the plugin creates a small server-id file inside plugins/WardenAC/. This is how a server keeps its identity in your dashboard across restarts, so its history and name stay attached to it. You don't need to touch this file — just don't copy it between different servers, or they'll appear as the same one.
Keep your key private
Your network key authenticates servers to your account. Treat it like a password: don't commit it to a public repo or paste it in screenshots. You can view it anytime in the dashboard's Settings.