Skip to content
ServerTrace

Quick rating

Community listing page, reviews may not be monitored by the author.

ServerTrace

No reviews yet

Server-only flight recorder for Forge servers: every event, packet, block change, slow tick and console error written to searchable text files on the server's disk. No commands, no screen, nothing for players to install.

Mod Loaders
Minecraft

About

Description

A flight recorder for your Forge server. ServerTrace writes down everything a dedicated server does between each start and stop: every event of Forge and of every mod, every network packet, every block change, every game event, slow ticks and every warning or error of the console. One line each, in plain text files on the server's disk, compressed once closed.

It exists to investigate strange problems afterwards: when a chest empties itself or a mod misbehaves once a week, the record is already there, and you search it for a player, a position, a class or a time. It is a raw technical trace for the server's owner: no screen, no languages, and nothing ever leaves the server.

Forge, Minecraft 1.20.1. Server only: players install nothing. Needs no other mod. MIT licence. Author: puercoalopecico.


Commands

ServerTrace is set up in config/servertrace-common.toml:

Setting Default What it does
enabled true Records anything at all
logPackets true Records network packets
aggregatePackets movement, chunks… Packets counted per second instead
aggregateEvents spawn checks, fluids… Events counted per second instead
keepDays 3 Older records are deleted
maxTotalMb 5120 Above this, the oldest go
rotateMb 256 Size of each file

Before you install

  • It writes a lot. On a server with a dozen players the old 1.0.0 wrote tens of gigabytes a day. 1.0.1 counts per second the packets and events that come by the thousand and say little one by one (movement, rotation, chunks, fluid checks, a mob's «may I grief» on every step…), keeps records 3 days and at most 5 GB, and says in the console every hour how much it wrote. A config written by 1.0.0 with its defaults gets the new ones.
  • Server only. On a client it does nothing.
  • Starts safely (1.1.1). While the server is still starting, the lines waiting for the record are capped like the rest (2 000 000 lines or about 128 MB): past it they are dropped and counted instead of taking the server's memory.

What a record looks like

config/ServerTrace/{date}-arranque/sucesos-0001.strc… (compact files; /servertrace export {file} gives the text back), one line per happening, fields separated by tabs: time, tick, thread, kind (EVENT, PKT_IN, PKT_OUT, BLOCK, GAMEEVENT, AGG, STATS…), name and key=value fields. A resumen.txt at stop with totals and the most frequent events and packets. A README.txt explains the format and how to search it.


Limits

  • Passwords of login mods are hidden in commands (login ***).
  • The record is as complete as the disk allows: when the writer falls behind, the game waits for it at most 2 seconds per line, never freezes, and what is dropped is counted.
  • It records; it does not explain. Searching a record is up to you (any text tool works).