Discover endpoints, inspect observations, and keep the evidence for future calculations.
Connect to your local history
Paste the pairing token printed by npm run server. Pair the extension separately using its Gameplay logger link.
DISCOVER FIRST
Gameplay endpoints
JSON is enabled only for selected endpoints. New endpoints contain metadata only unless you enable automatic capture. Disable JSON to add an endpoint to the ignore list; ignored endpoints keep metadata. The extension picks up changes on its next sync. Browser metadata and page payloads appear as separate observations; they are not separate game actions. Account routes and communications remain excluded.
Method
Path
Observations
Last received
Payload capture
Daily statistics and spells
Only observed days appear. Missing days are gaps. Unknown values are shown as —. News-backed spells have no inferred action timestamp; uncertain overlaps are excluded from combined totals.
Player and ally flags reflect the captured player’s perspective. Rank rise is movement, not absolute rank.
Daily kingdoms
World day / scope
Kingdom / identity
Coalition
Land
Power
Race / age / marker
Changes / flags / observer
Coverage / source
Daily coalitions
World day / scope
Coalition
Land
Power
Members
Coverage / source
Daily generals
World day / scope
Position
General
Experience
Captured player / observer
Coverage / source
Spell history
World / personal day
Caster → target
Spell
Outcome
Attempted / succeeded / failed
Cast strength / cost
Action / first observed
Evidence / sources
Extraction warnings and unsupported observations
OBSERVATIONS, NOT VERIFIED GAME OUTCOMES
Recorded events
Captured
Player / turn
Kind
Screen
Endpoint
HTTP
Event and related request/result
HTTP status describes transport completion. Game-action success requires interpreting the game response. Missing bodies are labeled explicitly; old metadata cannot be recovered by enabling a rule later.