Concurrent players
The Steam concurrent-player figure as it stood when this site was last built. It is a timestamped snapshot. A static site has no server to poll Steam from, and the browser cannot call that endpoint directly.
No reading available
WARDOGS_STEAM_APP_ID is not configured.
The collector needs WARDOGS_STEAM_APP_ID set when npm run data:collect runs. Until it is configured, this page shows no player number at all.
What a concurrent count does and does not tell you
This figure is the number of people in the game at a single instant, taken from the Steam Web API at the time this site was last built. It is a snapshot, not a live feed, and the timestamp beside it tells you how old it is.
It cannot be live, for a structural reason. This site is static — there is no server behind it to poll Steam for you — and a browser cannot call the Steam API itself because Steam sends no CORS headers. A build-time snapshot with an honest timestamp is the accurate option; a number that claims to be live and is not would be worse than none.
Concurrents are not players. The number of distinct people who played this week is several times any concurrent reading, because not everyone is online at once. Concurrents also swing hard with time of day and region: a weekday morning and a Saturday evening are different worlds, and comparing one to the other tells you about the clock rather than the game.
Peaks are the more stable statistic. If you want to compare one week to another, compare peaks to peaks. A single mid-week reading compared against a weekend peak will always look like a collapse.
For an Early Access title, watch the floor. A launch spike always decays. What matters is the level it settles at and whether content updates move it — that is the signal, and no individual reading contains it.
If the collector could not reach Steam when the site was built, this page says so rather than showing a stale figure as if it were current.