Enshrouded Metrics: Your Server's History and Player Statistics

Where Metrics is

Open your server and click Metrics in the sidebar, just below Events. It is there in every state, stopped servers included, and a deactivated server keeps it so you can still read its history.

Metrics is yours. Only you and the people you give panel access to can see it, and nothing on the page is shown to your players unless you switch it on (see "Privacy" below).

On an Enshrouded server it answers the things owners usually want to know. How many evenings a week does the group actually play, and for how long? Who has not logged in since the last update? Where in Embervale do people spend their time, and where do they keep dying? Is the world getting slow to save as the bases grow?

On an Enshrouded server the page has these tabs:

The general guide to every card, range and button is Metrics: Your Server's History. This article covers what is specific to Enshrouded.

How GameGrid collects Enshrouded data

Two things on your server feed Metrics: Enshrouded's own server log, and the GameGrid server module, which GameGrid places beside your server so the platform can see who is online, where they are, their deaths and their chat. It is the same module the live map and item delivery use, and nobody installs anything to play.

Who a player is on Enshrouded

Every player is identified by their Steam ID, so one person stays one player whatever their character is called, and a player who makes a new character keeps their history. On a player's profile, the account owner and administrators see the Steam ID with a Copy button, and the search box in the player list accepts a name, a character name or a Steam ID.

A death or chat line the server module cannot put a name to still counts for the server, as "a player", and is not added to anyone's profile.

The Overview

Untick or reorder cards on the Settings tab, or with ⚙ Layout at the top of the page.

Server health, uptime and restarts

The Server health summary reads like "Availability 96.4% · Uptime when meant to be on 99.1% · 1 crash · 3 restarts (2 scheduled, 1 Event Manager)".

• Availability is the share of the range the server was running.
• Uptime when meant to be on leaves out the time you meant it to be off: after you stop the server yourself, that time does not count against it until you start it again.
• Every restart is named by its cause: Owner (you, from the panel, the API or the Discord bot), Scheduled restart, Event Manager, Command Manager, Update or move, Crash recovery, Exited by itself, Crash, Host unreachable, Deactivated, or Other when nothing recorded why.
• A grey band labelled server module unavailable: player data unknown marks minutes the server ran but the server module did not answer, so who was on is not known for those minutes. It is not "nobody played". A minute or two of it while the world loads is normal.

The Health tab adds Availability per day, Outages (every stretch the server was meant to be on but was not), Time to ready (how long starts take, on average and for nine starts in ten), CPU, Memory, Network, Disk used, Backups and Game updates and mods.

Performance: save time, entities, ping and bases

Enshrouded does not report a frame rate or a tick rate, and Metrics does not make one up. What it does write into its log, each time it saves the world, is how long the save took, how many entities the world holds and how many bases there are. Those are the figures the Health tab draws.

• Save time is how long each world save took, in milliseconds. On a young world it is small. It grows as players build, because every base is part of the save. A save time that keeps rising week after week is the clearest sign the world is getting heavy for the server.
• Entities is the number of entities the game counted at its last save, which grows as the world is explored and built on. Read it next to save time; when both climb together, the world itself has grown.
• Player ping is the average ping of the connected players, from the connection report Enshrouded writes every 30 seconds. If one player lags and the average is fine, the problem is their connection.
• Bases over time is how many bases the world holds. It is a quick way to see a new server filling up after launch.

Ping is measured only while players are connected. What to change when the server struggles is in Enshrouded Server RAM, Performance and Player Limit.

Busiest hours

The Busiest hours tab shows the grid at full size. Switch between Average players and Peak players, Unique players and New players, and tick Include offline time to count the hours the server was off as empty. Below it are your Top 5 slots and Best time for an event, which opens the Event Manager with that time filled in.

Players, sessions and profiles

The 👥 Players button opens a list of everyone who has played on your server; the Players tab ranks them (Rank, Player, Logins, Deaths, Suicides, Playtime, Distance, Last active), and the Sessions tab lists every session with its length and distance. Each name opens the player's profile: playtime, sessions, deaths, distance, places discovered, the names they used, where they spend time and their latest activity. Full detail: Metrics: Player List and Player Profiles.

Import history from logs (on the Settings tab) reads the Enshrouded logs still on your server once, up to 30 days back, and adds the sessions they record from before player statistics started. Running it again adds nothing new.

Combat: deaths

Enshrouded has no player-versus-player combat, so Metrics records deaths and no kills. The Combat tab has three views:

• Kill feed: every death, newest first, with who died and when.
• Kill map: your live map with the deaths layer, so you can see where players die most.
• Deaths by cause: every death by what caused it, where the server module says.

Each player's profile has its own Combat tab with their deaths by cause, deaths per day and their longest life.

Travel and places

Travel shows your server's own live map of Embervale with Density, Trails and Deaths / Kills layers. Pick all players, up to 20, or one player's session, and press Play to replay the trails. Beside the map: total distance, time moving and idle, teleports and respawns left out (a teleport you make from the panel is marked as one), average and top speed, the top travellers and distance per day. Distances are in the game's world units, counted as metres, and the tab says so.

A place on Enshrouded is:

• POIs: the named places of Embervale, with their names as the game shows them;
• Spires: the Ancient Spires, the fast-travel towers;
• Regions: the regions of Embervale, such as the Springlands and Revelwood;
• Grid: the lettered and numbered squares the live map draws.

A player can be in several places at once: standing next to a spire in the Springlands counts for the spire, the region and the grid square. Use the kind filter to look at one kind at a time. Comparing the regions over a few weeks shows how far your group has pushed into the Shroud and where they keep going back to.

Places ranks them by time spent, visits or visitors and opens each one: time spent per day, its busiest hours, who spends most time there, who visited first and the deaths there. Positions older than 30 days are kept only as each session's simplified path and as time per grid square.

Events, economy, activity and chat

• Events lists Event Manager settings windows, Command Manager runs, prize events, and the server's stops and crashes. Open a row to see who took part.
• Activity is one timeline of chat, joins and leaves, deaths, purchases, moderation and the server's own history, with filters and a search.
• Chat is what players type in game, from the server module. Enshrouded has no player commands, so every line is chat.
• Economy shows coins earned and spent, how coins are earned, how wealth is spread, the items bought most beside how each delivery ended, the richest players (named only to the server's owner and administrators), kits and refunds, on a server that uses the GameGrid economy. See Enshrouded Economy Overview.

Only the server's owner and administrators can read chat text. Everyone else sees that a message was sent, not what it said.

The live status bar

The server's Overview page and the Metrics page show a status bar. On Enshrouded it can show: Status, Players online, Entities, Admins online (players in a user group with the Kick/ban permission, see User Groups), Uptime, Server time, Next restart, Ping, Uptime when on (7 d) and Peak today. Press ⚙ to choose and order them. While the server is stopped the game figures say not running.

Ranges, time zones, tables and downloads

• The bar at the top picks the range: Live (the last 15 minutes, refreshed every 10 seconds), 1h, 24h, 7d, 30d, 90d or your own dates. Granularity sets how wide each step of a chart is, and Compare to previous period draws the period before as a dashed line with the change beside each headline number.
• Every time is shown in your own time zone, named in the bar; the change link goes to your account page.
• Show as table on any card swaps the chart for the same figures as a table. The card's ⋯ menu has Download CSV, and Export downloads every card on the tab.
• The detailed record goes back seven days; before that charts are filled from hourly records and say "Hour-grained before" and the date.

Privacy: what is recorded about your players

• Player statistics are recorded from 6 October 2026, when version 1.1.0 of GameGrid's Privacy Policy took effect. Apart from sessions added with Import history from logs, nothing about players was recorded before that, and a chart that reaches further back marks where recording began with Not recorded before and the date. The server's own history (uptime, restarts, CPU, memory, players online) goes back further.
• Player IP addresses are never shown or stored by Metrics: not on any page, in any download, in the API or in the Discord bot.
• Player access (Metrics, Settings) decides what your players can see. Every switch is off until you turn it on: live positions on share links, leaderboards, posts to Discord and player self-service.
• Forget this player, on a player's profile under Admin, deletes their positions, places and names from Metrics on all your servers and keeps their statistics as "Deleted player", so your totals stay right.
• Positions are kept 30 days, sessions and deaths 365 days, chat 180 days.
• Resetting the world keeps every statistic. Start a new stats season when you want a fresh start: Metrics: Stats Seasons and Wiping Player Stats.

Full detail: Metrics and Your Players' Privacy.

Moderation and possible alternative accounts

On an Enshrouded server Metrics can suggest that two players may be the same person when they are linked to the same Discord account or use the same game account. A suggestion is a hint, never proof, and nothing is done automatically. You can also put a player On Watch, keep notes and set Alerts (a watched player connects, a chat keyword). See Metrics: Moderation, Possible Alternative Accounts and On Watch.

Discord: /metrics, /leaderboard and /my

Your GameGrid Discord bot reads Metrics with the server's API key. Create that key with the Discord bot preset, which includes the Metrics read scopes (The GameGrid Discord Bot on Enshrouded).

• `/metrics` for your staff: summary, uptime and peak (which may be posted in the channel), top, player, places, sessions and killfeed (always private), and new-season. The moderation subcommands alts and watch need the player_metrics:alts and player_metrics:write scopes added to the bot's key, which the preset leaves out. On Enshrouded, /metrics top can rank by Playtime, Deaths, Distance, Sessions or Logins, and /metrics killfeed lists deaths.
• `/leaderboard` for everyone, once you switch it on. An Enshrouded server is offered Deaths, Longest life, Playtime, Distance travelled, Places discovered, Event wins and the Milestones feed, plus Top earners and Wealth with the GameGrid economy. Turn on Posted leaderboards or the /leaderboard command under Metrics, Settings, Player access, then set each board up in Players → Leaderboards or with /leaderboard setup. See Metrics Leaderboards.
• `/my` lets a player read their own statistics: /my stats, /my playtime, /my travel, /my wealth, /my events. Switch on Discord /my and tick the sections to share under Metrics, Settings, Player access, Player self-service. Players must link their Discord first (Linking Discord Accounts to Enshrouded Players). See Player Self-Service.
• Deaths in Discord: switch on Post every kill to a Discord channel under Player access, and choose the channel with /config killfeed-channel. On Enshrouded, which has no kills, the bot posts each death.

The Customer API

Everything on the Metrics page is in the Customer API too: server history, busiest hours, places, players, sessions, deaths and CSV downloads. Server history needs the metrics:read scope and player data player_metrics:read. See The Customer API on Enshrouded and API Scopes.

Troubleshooting

• No Players, Sessions, Travel or Combat tab. These appear once player statistics are recorded and someone has played since. If the page shows "Player recording starts" with a date, they appear from then.
• A card says "No ... between" two dates. Nothing happened in that range, or the server was not running then. Try a longer range with Widen to 90 days.
• "server module unavailable: player data unknown" on Server health. Positions, deaths and chat come from the server module. A short stretch while the world loads is normal; a long one means the module was not running on that start. Restart the server, and contact support if it stays.
• Save time, entities and bases have gaps. Enshrouded writes them only when it saves the world, so a quiet server shows fewer points.
• There is no FPS tile or kill figure. Enshrouded reports no frame rate and has no player-versus-player combat, so Metrics shows save time and deaths instead.
• A death is not on a player's profile. It was counted as "a player" because the server module could not tell who died.