ServerRegister
Forge 1.20.1 server recorder: logs every event, chat, command and the whole console to text files; admins search them in game, inspect blocks, chests, mobs and player profiles. Also catches and explains client crashes. Needs Server Logistics.
The flight recorder of a Minecraft server. ServerRegister writes down everything that happens on the server — who broke that block, who emptied that chest, who killed that named horse, what was said in chat, what the console printed at three in the morning — in plain text files, and gives the players you grant access an in-game screen to search it, a profile of every player, and an analysis mode to point at any block, container, creature or player and read its history on the spot.
On every player's own game it is also a crash catcher: when the game is about to close because of an error, it saves the report, explains in plain words what went wrong and which mod it points at, and takes the player back to the menu instead of closing.
Forge, Minecraft 1.20.1. Requires Server Logistics. Required on the server and on every player's game. MIT licence. Author: puercoalopecico.
Commands
| Command | What it does |
|---|---|
/serverregister |
Opens the Server Log screen |
/serverregister analysisMode |
Enters or leaves the analysis mode |
/serverregister player {name} |
A player's profile |
/serverregister status |
Lines written, queued and dropped |
/serverregister crashes |
Your own game's crash list (anybody) |
serverregister access grant {player} |
Console only: gives the upper tier |
/serverregister access add / remove {player} |
Gives or takes the lower tier |
/serverregister access list |
Who has access |
Being a server operator gives no access: the console names who administers it. Nobody sees anything until somebody is granted.
Before you install
- On the server and on every player's game (it has items of its own, which the game needs on both sides), with Server Logistics.
- Volume. By default it writes what somebody or something is responsible for, plus fire, leaves and things appearing or disappearing by themselves. Water and lava flowing (
naturalFluids) and the environment — snow, ice, grass, farmland, crystals growing (naturalEnvironment) — are off: on a busy server they were most of the file. A block that only changes its state by itself (the «distance» of leaves) is never written.
What it records
Joins and leaves (with the position), chat and commands, deaths and kills, damage, every block placed, broken or changed and by whom (players, their arrows and pets, explosions, fire, pistons, commands), containers opened and what went in and out, doors, buttons and plates (a creature's door only when it really moved), items dropped and picked up, advancements, dimensions, teleports, and the whole console. One file per day and per start, plain text.
The screens
- Server Log: every entry, newest first, with filters by kind, player, place and time, and a search.
- Players: everybody who ever joined, with their names, time played, last position, inventory and ender chest as last saved.
- Analysis mode: point at a block, a container, a creature or a player and read its history.
- The whole console: what the server printed, searchable.
The crash catcher
On a player's game: a crash is saved in crash-reports, explained (which mod, why, what to try), and the game goes back to the menu. Every report is listed behind «Crashes» in the Options screen or with /serverregister crashes. With Crash Assistant or Not Enough Crashes installed it saves and explains, then leaves it to them.
Compatibility
- Works with PrankLevels and Factions&Wars: their events (prank levels, bases, factions, wars, alliances) go to its log.
- Languages: English, Spanish, French, Portuguese and German (and their regional variants); the rest in English.
ServerRegister Team
