How to Find What Is Lagging Your Server with LagGoggles

Start a Profiling Session

LagGoggles works by sampling what the server is doing over a period of time, so you need to let it run while the lag is actually happening. Open the LagGoggles interface (default keybind, or via the mod's menu entry) and start a profiling run. Play normally — walk around, let machines tick, trigger the farms or mob spawners you suspect — for at least a minute so the profiler collects enough samples to be meaningful. Short runs give noisy results.

Read the Results

When you stop the run, LagGoggles presents a ranked list of the worst offenders, typically grouped by block, entity, or chunk. The top entries are where the most tick time is being spent. Click or select an entry to see more detail, such as the position and the type of object responsible. Use the in-world highlighting to jump to the offending location — LagGoggles can outline or mark the blocks and entities it flagged so you can physically walk to them.

Act on the Findings

Once you know the culprit, decide whether to optimize, throttle, or remove it. Common fixes include reducing the number of active machines, breaking large clusters of tile entities, or culling excessive mobs. Re-run the profiler afterward to confirm the tick time dropped. Repeat the profile-fix-verify loop until the worst entries are acceptable.