wardogsgame.winIndex: wardogs data methodology / verification standards

Published: Sep 10, 2026Updated: Oct 03, 2026Data as of: Registry v2.0 · no unsourced regional telemetry

wardogsgame.win Technical Methodology & Verification Standard

This page states exactly which numbers come from which public interface, how often they update, and which statements are site inferences. If a figure cannot be traced, it is removed — not approximated.

1. Steam concurrent players

Source & refresh

Live count: Valve ISteamUserStats/GetNumberOfCurrentPlayers/v1/ for AppID 1867240, proxied by this site at /api/steam-players (browser CORS blocks direct Steam calls).
Store context: Steam store AppID 1867240
All-time / 24h peaks: dated third-party chart samples (SteamPeaks, SteamRaw) with outbound links on /server-status/. These are not silently substituted for each other.
Update frequency: live count on page load / manual refresh; peak tables when public chart samples are re-checked.

2. Evidence labels

Confirmed / Reported / Unconfirmed

[Confirmed]: Direct official or Valve API payload we fetched, with a link.
[Reported]: Reproducible public third-party or multi-source community documentation with a link.
[Unconfirmed]: Our inference (for example “likely up” when Steam still returns a player count and Steam news shows no outage). Always marked as ours.

3. Explicitly not measured (yet)

Removed rather than fabricated

We do not publish regional ping/packet-loss matrices, server tick-rate figures, map-area metrics, or unnamed DDoS timelines unless we operate documented probes or can cite a primary source. Steam's public player API does not provide those fields. Maintenance detail beyond linking Steam news is withheld when unsourced.

Related tools: /crashing/, /system-requirements/, /wiki/.

Corrections

Send verifiable primary sources to contact@wardogsgame.win. Unsourced screenshots alone are not enough to reinstate a deleted metric.