TRACKER MAP UPDATED: —LAST CHECK: —NEXT CHECK: EVERY 30 SECONDS
Waiting for the first full-map response.
CONNECTING…TRACKER FEED STATUS
ALLIANCE POWER INDEX
ALLIANCE DATABASE
LAST KvK // BATTLE REPORTLOADING HISTORY
WAITING FOR HISTORICAL KvK DATA
—IMPORTED / DISCOVERED—WITH SANCTUARY COORDINATES—NOT IN AN ALLIANCE—CONFIGURED MONITOR ZONES
RECENT KvK OPERATIONSHISTORICAL RECORD
SERVER 324 // TACTICAL WORLD MAPCOORDINATE GRID · X/Y
SOLO PLAYER ROYAL CITY MUD / CURSED LAND DETECTION RADIUS0 MAP MARKERS
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.
ROYAL CITY MONITORSANCTUARY POSITION SCAN
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.
KVK EVENT CONTROLEVENT HISTORY
Only administrators can create or close events and collect snapshots.
KVK POWER LOSS & RECOVERY INTELLIGENCEOBSERVED MIGHT CHANGES BETWEEN SNAPSHOTS
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.
—IN SELECTED EVENT—UID MATCHED ACROSS SNAPSHOTS—SUM OF DOWNWARD CHANGES—SUM OF UPWARD CHANGES
KVK PARTICIPATION INTELLIGENCE2 CONSECUTIVE SNAPSHOTS · MUD COUNTED AREA
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.
—2 CONSECUTIVE SNAPSHOTS—DETECTED ONCE SO FAR—INSIDE COUNTED AREA—NO DATA
ALLIANCE PARTICIPATION / POWER SHAREFULL POWER VS CONFIRMED MUD POWER
Collect a snapshot to initialise participation intelligence.
PLAYER PARTICIPATION STATUSLIVE ROSTER
No participation records yet.
PLAYER POWER LOSS RANKINGSOBSERVED MIGHT DROPS
Ranks players by observed Might decreases between consecutive snapshots. This is not a confirmed troop casualty count.
PLAYER RANKINGSSELECT RANKING
PLAYER POWER RECOVERY RANKINGSOBSERVED MIGHT GAINS
Ranks increases in Might between consecutive snapshots. Increases are not proof of healing.
PLAYER RANKINGSSELECT RANKING
ALLIANCE POWER RANKINGSGROSS DROPS / GAINS / NET CHANGE
ALLIANCE POWER MOVEMENTATTRIBUTED TO ALLIANCE AT LATER SNAPSHOT
Two or more snapshots in an event are required.
KVK POWER MOVEMENT TIMELINESUCCESSIVE SNAPSHOTS
POWER MOVEMENT TIMELINEBETWEEN SUCCESSIVE SNAPSHOTS
MUD PRESENCE HISTORYFIRST / LAST DETECTION
HISTORICAL KvK INTELLIGENCE · SERVER 324SERVER 324
—SERVER 324 HISTORY—SERVER 324 ONLY
BATTLE HISTORYSELECT A BATTLE TO VIEW ALLIANCE RANKINGS
Waiting for first historical import.
ALLIANCE MIGHT LOSSESSELECT A BATTLE
Select a battle above.
ALLIANCE DATABASEPOWER RANKING
PLAYER DATABASESEARCHABLE ROSTER
WAR ARCHIVEEVENT HISTORY
ADMIN CONTROL // RESTRICTEDAUTHORISED SESSION
CREATE KvK EVENT
ADD ROYAL CITY
IMPORT PLAYER DATA
CSV headers: uid,name,alliance_tag,power,x,y. Use SOLO for unaffiliated players. JSON array is also supported.
ADD PLAYER MANUALLY
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. Do not set DEMO_MODE=false until the Tracker adapter and API key have been verified.
324 WATCHTOWER // LIVE DATA COLLECTION
COLLECTING SNAPSHOT
Sending collection request to Watchtower…
ELAPSED 00:00
1Request accepted by browser
2Tracker / roster collection in progress
3Saving snapshot and updating intelligence
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.
RESTRICTED ACCESS
ADMIN AUTHENTICATION
Enter the administrator token configured in the server .env file.