Minecraft Player Journey Control Center

Player Journey Control Center

Live event state + deterministic historical replay

Live event stream
Population changes only when real JOIN / LEAVE / CHAT / DEATH events arrive. Integration hook: window.ingestMinecraftEvent(event).

Waiting for events

Lifecycle rules

New · max tenure (days) New · max sessions Returned · min sessions Returned · within first days At Risk · no JOIN for days Churned · no JOIN for days

Core rules

Core · min tenure days Core · min total sessions Core · signals required Signal · sessions / 7d Signal · playtime min / 7d Signal · CHAT / 7d

Observed signals only.
CHAT and DEATH are analytics inputs from real events. They do not cause synthetic returns or future behavior.

Live · current state from incoming events

Drag: orbit Right-drag: pan Wheel: zoom

Waiting for players · Journey insights appear as the server develops.

LIVE TIME

—

initializing

Online 0

No rendered NPCs online

Server Health

—

retention-weighted

Activation

—

configured return rule

D7 Retention

—

new cohort return

Core Share

—

high recent engagement

At Risk

—

dormant, not yet churned

New Active Core Dormant Churned

Acquired → Returned → Core · recency → At Risk / Churned

Player Journey

Lifecycle progression, retention signals and diagnostics in one view.

Current picture

DAU

MAU

Avg playtime / DAU

session depth

Chat activated

≥1 CHAT in last 7d

Waiting for players

The control center starts at population 0.

Journey funnel

Acquired

Returned

Core

Current status

New

Active

Core

At Risk

Churned

Community signal

Needs enough first-week cohorts to estimate chat association.

Diagnostic: deaths/10h — · events today 0

Population trend

Behavior & retention trend

Raw event stream

Event schema

JOIN { player_id, name, timestamp } LEAVE { player_id, name, timestamp, duration_minutes } CHAT { player_id, name, timestamp } DEATH { player_id, name, timestamp } SERVER_START { timestamp } SERVER_STOP { timestamp } name is an attribute on player events. Replay sorts by timestamp and streams events according to their original time gaps × the selected replay-speed multiplier.