Moderation

The Logs explorer for payments, trades and punishments, abuse flags, punishments, staff activity and bans across servers.

Using the dashboardUpdated 2 min read

Moderation needs an agent and the permission to read players.

Logs

A searchable event log: payments, shop and auction sales, trades, punishments, votes and more, with filters for type, player, counterparty, currency, amount range, source and any property, plus a histogram and a field list. Save a search and share it with your team. History follows your plan. Download rows as CSV (Operator) or JSON Lines (Network).

Flags

Abuse flags computed from game events only: for example large transfers, money funnelled from new accounts into one account, transfer rings, or staff giving themselves money. Free shows only the large-transfer flag, in the app and without alerts; Operator and Network show every rule. ServerStats never uses IP addresses to find alt accounts, because it never receives them.

Punishments

The punishments dashboard for the server's gamemode. Reasons are stored as a category by default; the text is stored only if an owner or admin opts in (Operator and Network), and every read of it is audited.

Staff activity

Punishments per staff member. A moderator sees only their own row unless the role has read_staff_all.

Bans (organisation tab)

Active bans across servers, built from the ban and revoke events your agents report. Network lets you see all servers at once and push a ban or unban to several servers in one action. A pushed ban is signed; servers whose agent cannot take bans, or that have remote actions off, are skipped with a reason.

Operator and Network also get Templates and Pre-bans (ban an ID before the player joins). See Ban templates and pre-bans.

Remote actions

Kick, ban, mute and message from the dashboard are off by default. They need two switches: moderation in the agent's config and Remote actions in the server's Settings. Each action is signed and recorded in the audit log.

Still stuck? Email [email protected] with the server name and what you see. For a rejected claim code or no data, include the output of the agent’s status command.