INTELLIGENCEEXPLORE PLAYERS ↗

Operational overview and alliance intelligence



Waiting for the first full-map response.

This is a coordinate plotting map, not the game's original terrain artwork. The Royal City and four turrets are preloaded. The estimated outer MUD boundary is X446–554 / Y446–554. The orange COUNTED AREA is X448–552 / Y448–552. The narrow 1-coordinate strip between the outer grey edge and inner orange edge is the NO-COUNT SAFETY ZONE and is excluded from MUD presence. Use FIT MUD to zoom into this region or FULL WORLD to see the entire 1000×1000 grid. Player markers appear only after player data is imported or collected. Click the grid to read X/Y coordinates.
Plan alliance positions on a separate editable board. This planner does not alter live player coordinates, the world map, or tracker imports.
Click or drag across cells to paint. Select MOVE LANDMARK, then drag Royal City or a tower to another cell. Save Layout stores this plan on the Watchtower server.
Presence includes only player Sanctuary coordinates inside the COUNTED AREA (X448–552, Y448–552). The 1-coordinate NO-COUNT SAFETY ZONE between that area and the estimated outer boundary (X446–554 / Y446–554) is excluded. Individual Royal City radii remain separate. It does not track marches or prove combat participation.
A pre-event baseline begins 30 minutes before KvK. During the event, snapshots are saved only when a new map version is imported (map refresh every 15 minutes). The final snapshot uses the first new map after the event ends. Administrators can end an active event early; Watchtower waits for the next new map version before finalising it.
Tracks gross drops, gross gains and net change for players and alliances. Missing players are not treated as zero. Might changes are not proof of troop casualties or healing.
A player is CONFIRMED only after appearing inside COUNTED AREA in two consecutive snapshots for the same KvK event. Power is shown in two separate measures: the alliance's full roster power and the confirmed MUD players' power share. Not detected in MUD does not mean inactive elsewhere in KvK.
Collect a snapshot to initialise participation intelligence.
No participation records yet.
Ranks players by observed Might decreases between consecutive snapshots. This is not a confirmed troop casualty count.
Ranks increases in Might between consecutive snapshots. Increases are not proof of healing.
Waiting for KvK analytics.
Two or more snapshots in an event are required.
Waiting for first historical import.
Select a battle above.
Immutable weekly TOP 20 snapshots generated from the latest full-map Survivor Database. Rankings are independent of KvK snapshots and are never recalculated retrospectively.
The first snapshot will be created Friday at 12:00 UK time.
No weekly snapshots have been archived yet.
Combined alliance priority for city selection. Uses the latest archived Weekly TOP 20 and the latest completed official KvK final alliance ranking. Rank scale: #1 = 100 points, #20 = 5 points, #21 and below = 0 points. Missing source ranking = 0 points.
Loading City Priority ranking…
The ranking is calculated from the saved source rankings; no additional tracker API calls are made.
Automatic MUD snapshots: −30 min, −15 min, start, every 16 min, final at +120 min.
CSV headers: uid,name,alliance_tag,power,x,y. Use SOLO for unaffiliated players. JSON array is also supported.
Admin token stays in browser memory only. Central Royal City and four turrets are seeded automatically on a fresh database. Enable HTTPS before exposing the service publicly. Live player snapshots use the public full-map feed; authenticated alliance/profile roster calls are not used.
Sending collection request to Watchtower…
Collection time depends on Tracker API response. This indicator shows that the request is running; it does not invent a percentage or claim live API progress.