Windrose 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 a Windrose server it answers the questions owners usually ask us. Why did the server restart on its own two days after the last one? When is the crew actually online? Is the world still saving? How far do players sail in an evening, and where do they keep dying?

On a Windrose 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 Windrose.

How GameGrid collects Windrose data

Windrose Metrics reads Windrose Plus, which GameGrid installs and keeps up to date on every Windrose server (Windrose Plus Guide), and the game's own log.

Who a player is on Windrose

Windrose tells the platform each player's character name and no account id, so on Windrose a player is their character name. The cards say "Players are identified by character name." A player who renames their character looks like a new player, and two players with the same character name are counted as one. Because of that, a Windrose profile shows no ID line, and the player list is searched by name.

The Overview

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

Server health, uptime, restarts and the 48-hour exit

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, Planned exit by the game, or Other when nothing recorded why.
• Planned exit by the game: on a server players join with an invite code, Windrose ends its own session about every 48 hours. GameGrid recognises the lines the game writes when it does, draws that stretch in its own colour on the band, and counts it as a restart by the game, never as a crash. The server comes back by itself.
• A grey band labelled status file unavailable: player data unknown marks minutes the server ran but Windrose Plus's status file was not being updated, so who was on is not known for those minutes. It is not "nobody played".

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: tick rate, entities and world saves

Windrose reports an engine tick rate, not frames, so Metrics calls it Tick rate. The Health tab draws:

• Tick rate: engine ticks per second, worked out from the game's own log. A healthy Windrose server runs at about 30. A line that sags well below that while players are on is the server struggling.
• Entities: the creatures and resource nodes Windrose Plus's live map counts.
• Time since the last world save: how long ago the game last saved the world successfully. It rises and falls back to near zero at every save, like a saw blade. A line that keeps climbing without dropping means saves are not finishing. Take a backup and contact support if it keeps climbing.

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, 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 Windrose Plus's activity 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

Windrose reports deaths and no player kills. Deaths are read from the status file every 10 seconds, so a death and respawn quicker than that can be missed, and the cards say "Deaths sampled every 10 s." 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, at the last place each player was seen alive.
• Deaths by cause: the status file says that a player died, not what killed them, so Windrose deaths are grouped as Unknown there.

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

Travel and places

Travel shows your server's own live map, the sea chart, 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, jumps left out, average and top speed, the top travellers and distance per day. Distances on Windrose are approximate, and the tab says so.

A place on Windrose is:

• POIs: the points of interest on the sea chart, each counted within about 150 metres of its marker;
• Islands: the island the chart is drawn around;
• Grid: the lettered and numbered squares the live map draws.

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. The chart itself is described in Windrose Plus Live Map (Sea Chart) Guide.

Events, economy, activity and commands

• Events lists Event Manager settings windows, Command Manager runs, prize events, and the server's stops, crashes and planned exits. Open a row to see who took part. Windrose has no in-game broadcast, so Event Manager restart warnings reach players through your Discord bot only.
• Activity is one timeline of admin commands, joins and leaves, deaths, purchases, moderation and the server's own history, with filters and a search.
• Admin commands are the console commands Windrose Plus ran for the server: the Command Manager, commands sent from the panel console and the economy's deliveries. Windrose has no in-game chat, so Metrics records no chat on Windrose.
• 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 Windrose Economy and Shop.

The live status bar

The server's Overview page and the Metrics page show a status bar. On Windrose it can show: Status, Players online, Tick rate (with a line of the last 15 minutes), Entities, Uptime, Server time, Next restart, 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 this server (Windrose players are identified by character name, so per server) and keeps their statistics as "Deleted player", so your totals stay right.
• Positions are kept 30 days, sessions and deaths 365 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 On Watch

On a Windrose server you can put a player On Watch, keep notes on them, and set Alerts for when a watched player connects; Metrics can also suggest two players are the same person when they are linked to the same Discord account. A suggestion is a hint, never proof, and nothing is done automatically. 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 (Discord Bot Setup).

• `/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 Windrose, /metrics top can rank by Playtime, Deaths, Distance, Sessions or Logins, and /metrics killfeed lists deaths.
• `/leaderboard` for everyone, once you switch it on. A Windrose 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. On Windrose a player links by running /link with their character name and joining the server (leaving and joining again if already on it); there is nothing to type in game (Linking Discord to a Game Character). 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 Windrose, which reports 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 Customer API 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.
• "status file unavailable: player data unknown" on Server health. Everything about players on Windrose comes from Windrose Plus's status file. A short stretch while the world loads is normal; if it lasts, check Windrose Plus on the Windrose Plus troubleshooting page.
• A restart every two days that you did not schedule. That is Windrose ending its own invite-code session, shown as Planned exit by the game. It is not a crash and the server comes back by itself.
• One person shows as two players. They renamed their character or play a second one: Windrose players are known by character name only.
• No places listed. Places come from the sea chart, which GameGrid generates for your world; see the Sea Chart guide for what its status means.
• There is no chat. Windrose has no in-game chat for Metrics to record; the card shows admin commands instead.