Look up players and sessions
The Players list, a player's profile — timeline, time per server, origin, sanctions and shared addresses — and the Sessions page.
In a few minutes you can find one player, read their history, see which accounts share an address, and list every visit to your network.
Before you start#
You need a linked proxy or standalone server that has seen the player join: a player appears after their first session, and a game server behind a proxy does not create players on its own. Some parts depend on a permission: amounts spent need the revenue permission, and the Address section needs Player IP addresses and shared-IP accounts. See Team and settings.
Steps#
Open Players
In the sidebar, open Players. The All players tab lists everyone who ever joined the network, one row each.
Find the player
Type a name, a UUID or a Discord name in the search box. Narrow the list with a Player group tab or the Identity filter (Premium, Cracked or Bedrock), and sort by Last seen, First seen, Playtime, Sessions or Spent.
Open the profile
Click the row. The profile opens with the header, key numbers, a playtime chart and the timeline.
Read the timeline and the sessions
Scroll to Timeline for stays, purchases, votes and punishments, then Recent sessions for how each visit ended.
Check shared addresses
In Address, Accounts sharing an IP lists other players who joined from any of this player's addresses.
Check that it works#
A player you know has joined appears in the list with a Last seen that matches and at least one session. Their profile shows Online in the header if they are connected now. If the list is empty, link a server first, see Connect your server.
Going further#
The list#
| Control | What it does |
|---|---|
| Player group tabs | All, or one lifecycle group: New, Loyal, Regular, Occasional, Fading away, Gone (30+ days). See the definitions. |
| Search | Part of a name, a full UUID, or a Discord name. |
| Identity | Premium, Cracked or Bedrock. |
| Sort | Last seen, first seen, playtime, sessions, or amount spent (the last only with the revenue permission). |
The columns are Player, Group, Country, First seen, Last seen, Days active (30d), Sessions, Playtime, Spent (revenue permission only) and Identity.
The profile#
| 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. A linked Discord account shows here too. | 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 game server, 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 and shared-IP accounts (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. |
| Economy, Market | Balances and market activity, when those modules are on. | Economy, market. |
| Other Exylia apps | What the player did in other Exylia services linked to the workspace. | Linked apps. |
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.
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, which means it missed three signals and is usually a crash. The session was closed at its last signal. |
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.
Tutorials and quests#
With ExyliaJourney on your servers, Players › Tutorials & quests fills in on its own: every journey it reports, with nothing to configure. Without it, the tab says what the plugin adds.
Tutorials & quests columns and details
| Shown | Meaning |
|---|---|
| Started | Players who started the journey in the period, each counted once, however many times a repeatable journey ran. |
| Finished | Of them, the share who completed it within 14 days. |
| Median time | Half of those who finished took less than this. |
| Skipped | The share who skipped the whole journey. |
| Abandoned | The share who stopped making progress (idle) or ran out of time on a step. |
Opening a journey shows every step in order: how many players reached it, completed or skipped it, how long they spent on it, and how the runs that ended there ended. The step that loses the most players is called out in red, and Stalled at this step lists who stopped there, linked to their profiles. Open as a funnel opens the built-in journey each one adds under Activity › Journeys.
For a journey that starts on the first join (the onboarding), the page compares the new players who finished it with those who did not: back the next day, a week and a month later, came back within a week, and bought something. Players › First steps adds the same comparison, a Finished the tutorial step in the new-player journey, and where the new players who never came back stopped in it. A player's timeline shows each journey run and how it ended.
Journeys are read from the events of the last 90 days. Older ExyliaJourney versions do not announce their journeys: names and steps then come from what players did.
First steps#
Players › First steps follows new players through their first days: New players, Left quickly, Back the next day, Back a week later, Bought something, and Why new players don't come back.
Sessions#
Open Activity › 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 game servers does not start a new one.
| Section | Shows |
|---|---|
| KPIs | Visits and Players in the range, Average visit and Typical visit (the median). |
| All visits | Player, Started, Join address, Country, Client, Ended and Length. Filter by Client (Java or Bedrock) and sort Newest or Longest. |
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