Low TPS and lag (how to fix)

Fix lag and low TPS on a Victus Minecraft server — measure TPS, tune view/simulation distance, control entities, and switch to Paper/Purpur.

Minecraft aims for 20 TPS (ticks per second). When TPS drops the whole world runs in slow motion — mobs stutter, redstone lags, blocks break slowly. Lag is usually caused by too much being simulated per tick (view distance, entities, hoppers, redstone) rather than the network. Fix the server-side load first.

Measure it

1. In the console (or in-game as op) run tps — Paper/Purpur reports the 1m/5m/15m average.
2. For a deep dive on Paper/Purpur run spark profiler (if the Spark plugin/mod is present) to see exactly what is eating tick time.
3. Watch the CPU graph in the panel while players are on — sustained 100% CPU with low TPS means you are overloading the plan.

Highest-impact fixes

• Lower view-distance to 6–8 and simulation-distance to 4–6 in server.properties — this is the single biggest lever.
• Switch to Paper or Purpur if you are on Vanilla/Spigot — they add major performance options (see "Switch software/JAR").
• In the Paper/Purpur config, cap entities, merge dropped items, and reduce mob-spawn ranges.
• Kill entity farms and lag machines; use /kill @e[type=item] sparingly to clear dropped-item pileups.
• Limit redstone/hopper-heavy contraptions, which are notorious TPS killers.