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
- 1In the console (or in-game as op) run
tps— Paper/Purpur reports the 1m/5m/15m average. - 2For a deep dive on Paper/Purpur run
spark profiler(if the Spark plugin/mod is present) to see exactly what is eating tick time. - 3Watch 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-distanceto 6–8 andsimulation-distanceto 4–6 inserver.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.
Server lag vs. your ping
If TPS is a steady 20 but you still rubber-band, the problem is your connection/ping, not the server. Test from another network and check the panel ping/allocation before changing server settings.
Some plans just need more CPU
Minecraft tick performance is mostly single-thread CPU bound. If you have tuned everything and TPS still drops under normal player counts, you have outgrown the plan — upgrade for more CPU priority.