Players and sessions
The Players list, a player's profile — timeline, time per server, origin, sanctions and shared addresses — and the Sessions page.
Players
Everyone who ever joined the network, one row each.
| Control | What it does |
|---|---|
| Segment tabs | All, or one lifecycle segment: new, core, regular, casual, at risk, churned. See the definitions. |
| Search | Part of a name, or a full UUID. |
| Sort | Last seen, first seen, playtime, sessions, or amount spent (the last only with the revenue permission). |
The columns are the player, their segment, country, first and last seen, days active in the last 30, sessions, playtime, and — with the revenue permission — what they spent.
A player appears after their first session. On a network that means after they connect through a linked proxy; a backend alone does not create players.
A player's profile
Clicking a player opens their page.
| Section | What it holds | From |
|---|---|---|
| Header | Name, UUID, online or offline, and a ban or mute that is still running, with its reason and end. | Sessions, punishments. |
| KPIs | First and last seen, playtime (with AFK and session count), active days in the last 30, amount spent net of refunds (revenue permission), votes, punishments issued, first hostname and its campaign, client brand and version. | Sessions, presence, votes, punishments, Tebex. |
| Playtime, last 90 days | Hours per day, with AFK stacked on top. | Presence. |
| Timeline | Stays on each server with their activity counters (chat, commands, deaths, kills), purchases and refunds, votes, punishments issued and lifted, newest first. | Presence, Tebex, votes, punishments. |
| Time per server | Active and AFK time on each backend, and when they were last there. | Presence. |
| Where they came from | First hostname and its campaign, country, client. | Their first session. |
| Address | Only for members with Player IP addresses (view_ips). See below. | Sessions. |
| Recent sessions | The last 50 network sessions: start, hostname, the server that reported it, language, how it ended and its length. | Sessions. |
How a session ended:
| Shown | Meaning |
|---|---|
| Online | Still open. |
| Quit | The player left. |
| Kicked | Kicked by a plugin or staff, or kicked by the proxy for logging in twice. |
| Server stopped | The server or proxy shut down cleanly while they were on it. |
| Timed out | The server that held the session went silent — it missed three heartbeats, usually a crash — and the session was closed at its last heartbeat. |
A stay that shows "still there or left without a leave event" belongs to a server that did not report the leave, typically because it crashed.
The address section
What it shows depends on the workspace's Player addresses setting (see Team and settings):
| Setting | Shown |
|---|---|
| Hash only | "Stored as a hash only" and the first characters of the hash. The address itself can never be read. |
| Encrypted address | The last IP, decrypted. |
Either way it lists accounts sharing an IP: other players who joined from any of this player's addresses, with when they were last seen. The match is made on the hash, so it works in both modes.
Sessions
A session is one network connection, from the moment a player connects to the proxy (or a standalone server) until they leave. Moving between backends does not start a new one.
| Section | Shows |
|---|---|
| KPIs | Sessions in the range, players and sessions per player, average and median length. |
| All sessions | Newest first: player, start, hostname, country, client, how it ended and its length. |
Because a session is a network connection, this list is always the whole network, whatever server the filter picks.
Something missing on this page? Tell us on Discord