A transparent look at how live Warcraft 3 lobby data is collected, processed, and served.
WC3Tracker aggregates live lobby data through a combination of publicly available Warcraft 3 lobby trackers and a proprietary API layer built specifically to maintain high-uptime, real-time coverage across all Battle.net servers. There is no official Blizzard API for this data — WC3Tracker is one of the few tools that has built the infrastructure to collect and preserve it reliably.
Every active lobby is captured as a snapshot including its name, map file, host BattleTag, server region, and current player count. Multiple data sources are cross-referenced to ensure accuracy and minimize gaps during outages.
When a lobby disappears from the feed, it is recorded as a completed session with its duration calculated from the first and last observed timestamp.
Warcraft 3 map files include version numbers in their filename — for example
DotA_v6_89Q.w3x and
DotA_v6_90c.w3x
are both DotA but tracked as separate files.
WC3Tracker strips version identifiers, numeric suffixes, and copy markers like (2)
to group all versions of a map together. This gives accurate lifetime statistics across the full history
of a map regardless of how many version updates it has received.
The player base metric counts unique BattleTag host identifiers per time bucket. A BattleTag that hosts 10 lobbies in one hour still counts as one unique host for that hour. This gives a true measure of how many distinct players are actively engaging with the custom game scene — independent of how prolific individual hosts are.
Tracking this over months and years produces a reliable signal for community growth or decline that cannot be gamed by a single active host opening many lobbies.
All lobby records are stored in a SQLite database. Aggregate statistics (sessions per map, unique hosts, fill rates) are pre-computed and cached for fast access. The live lobby view is served directly from an in-memory cache refreshed on each polling cycle.
Map and host pages at URLs like /map/dota and
/host/PlayerName are server-side rendered
on every request so they are fully indexable by search engines without JavaScript.