How to Fix Minecraft Server Lag: Find the Cause, Get TPS Back to 20, Stop the Crashes

Minecraft Server Lag Fix
Minecraft Server Lag Fix

To fix Minecraft server lag, first check the server’s TPS with /tick query or spark: if it’s below 20, the server is overloaded, and the usual fixes are lowering simulation-distance, pre-generating the world, and finding the farm, entity pile or plugin eating each tick. If TPS is a steady 20 and only some players stutter, the lag is on their PC or their connection, not the server. Here’s how to tell which one you have, the fixes in the order that usually works, and what to do when lag turns into crashing.

Server lag, client lag or network lag?

Three different problems all get called “lag”, and each has a different fix. Server lag hits everyone at once and shows up as a TPS drop. Client lag is low FPS on one player’s PC. Network lag is high ping or a weak upload, and makes players rubber-band even when TPS is fine. Work out which one you have before changing anything.

What you see Type Where to look
Everyone sees blocks reappear, mobs freeze, crops and furnaces slow down Server lag (low TPS) This guide
One player has low FPS or stutters while others are fine Client lag That player’s graphics settings and mods
Players rubber-band or time out, but TPS stays at 20 Network lag Ping, the host’s upload, server location

Check TPS first

A Minecraft server runs 20 ticks per second (TPS). Each tick must finish in 50 milliseconds (MSPT, milliseconds per tick) to keep that pace. When ticks take longer, TPS drops and the whole world slows down. Measure it before you fix anything, so you know whether a change helped.

  • Vanilla: /tick query (op level 3) prints the average tick time. Under 50 ms is healthy.
  • Paper bundles spark since 1.21: /spark tps shows TPS and CPU, /spark health adds memory and disk.
  • Find the cause: /spark profiler start --timeout 600 records 10 minutes while the lag is happening and gives you a link to a report showing which plugin, entity or task takes the time. Add --only-ticks-over 50 to record only the slow ticks.

Paper’s old /timings is deprecated and switched off by default since 1.21, so use spark.

How to reduce lag on a Minecraft server: the fixes that work

Most lag on Minecraft servers comes from the same few places: too much of the world being simulated, new chunks being generated while people explore, and builds that run every tick (farms, hoppers, redstone clocks). Work down this list, measuring TPS after each change.

1. Lower simulation-distance and view-distance

Both default to 10 chunks in server.properties. simulation-distance is how far from each player mobs, crops and redstone are updated, and it’s the bigger lever: dropping it to 6 or 8 cuts tick work sharply. view-distance is how far the server sends terrain; lowering it to 8 eases CPU and upload. Restart after editing. The Minecraft Wiki’s own advice for major lag is to reduce these first. All the other keys are in the server properties guide.

2. Pre-generate the world

Generating new chunks is some of the heaviest work a server does, and players flying with elytra trigger a lot of it. Pre-generate the area people will play in before they explore it, with the free Chunky plugin or mod (Paper, Fabric, Forge, NeoForge). In the console:

chunky radius 5000
chunky start

Then the Nether: chunky world world_nether and chunky start. chunky pause and chunky continue stop and resume it. Run it while nobody is online. Add a vanilla border so the world stops growing past what you generated: worldborder set 10000 (the value is the full width in blocks).

3. Fix the builds that run every tick

  • Hoppers constantly check the block above for items. Covering a hopper with a solid block, or better a composter, stops that check.
  • Redstone clocks and redstone dust cause floods of block updates. An observer clock left running in an unused farm is a classic: put a lever on clocks and switch them off when nobody’s there.
  • Mob farms and animal pens: every mob runs AI. Cap breeding pens, kill off surplus animals, and light up areas to stop hostile spawns.
  • Dropped items pile up around broken farms. Clear them with /kill @e[type=item], then fix the farm that’s spilling them.
  • Random tick speed: if someone raised random_tick_speed to grow crops faster, put it back to 3 with /gamerule random_tick_speed 3.

A spark report names the exact block entity or entity type, so you’re not guessing which farm it is. More on redstone in redstone optimization.

4. Run optimized server software

Vanilla server.jar has no performance tuning. Paper is a drop-in replacement (it converts a vanilla world for you) with many performance improvements and spark built in. On Fabric or NeoForge, the Lithium mod optimizes game logic and works on the server alone. Note that Fabulously Optimized is a client modpack: it speeds up a player’s game, not your server.

5. Give it the right amount of RAM

Too little RAM causes stutters from constant garbage collection and eventually OutOfMemoryError crashes. Too much doesn’t help: past a point, PaperMC notes, extra RAM is wasted. Vanilla and Paper usually need 2 to 4 GB, modpacks 8 GB and up; the full table is in the Minecraft server RAM guide. On Paper, Aikar’s flags (from PaperMC’s start-script generator) are the standard garbage-collector tuning.

6. Find the bad plugin or mod

If the spark report points at a plugin or mod, update it first; the fix may already exist. If you can’t tell which one it is, do what PaperMC suggests: disable half, test, and keep halving the group that still lags until one is left.

7. Check the hardware and the connection

The server runs mostly on one CPU core, so single-core speed is what matters, and an SSD makes chunk loading and saving faster. A Raspberry Pi can run a small vanilla or Paper world for a few friends, but it has little headroom for farms or mods: see Raspberry Pi 5 Minecraft server performance. For network lag, use Ethernet, check the host’s upload speed, and host close to your players.

Minecraft server crashing: reading the crash

When a server crashes it writes a crash report into the crash-reports folder and its log into logs/latest.log. Open the newest one and read the first lines of the error: the exception and the first mod or plugin named under it usually point at the cause. These are the common ones.

Crash or message Cause Fix
A single server tick took 60.00 seconds (should be max 0.05) The watchdog (max-tick-time, 60,000 ms) stopped a frozen server Find what froze the tick with spark; don’t just raise or disable the watchdog
java.lang.OutOfMemoryError Not enough RAM for the world or mods Raise -Xmx within what the machine has
UnsupportedClassVersionError Java too old for the Minecraft version Java 25 for 26.x, Java 21 for 1.20.5 to 1.21.11
Crash naming a mod right after you added or updated one Mod built for another Minecraft version or loader Remove it, or get the matching file
Crashes whenever someone goes to one area Something in those chunks, often a huge pile of entities Clear the entities there; if it still crashes, restore from a backup

If a mod crash appears right after an update, the update guide covers matching mods to the new version.

Minecraft server not working or not loading?

  • The window closes at once: read logs/latest.log; the usual culprits are the EULA not accepted or the wrong Java.
  • Stuck while loading the world: a big world or modpack can take minutes on first start; wait for Done in the console before connecting.
  • It runs but nobody can join: that’s networking, not performance; see port forwarding and connection errors.
  • LAN players can’t see it: they need the server PC’s local IP, and the PC’s firewall has to allow Java.

The longer checklist is in Minecraft server won’t start.

FAQ

Why is my Minecraft server so laggy?

Usually one of: too high a simulation distance for the hardware, players generating new chunks, farms and redstone running every tick, or one heavy plugin or mod. Check TPS and run a spark profile to see which.

What is a good TPS for a Minecraft server?

20, which is the maximum. That means each tick finishes in 50 ms or less. Anything lower and the whole world runs slower than normal.

Does more RAM fix server lag?

Only when the server is short of memory. If memory is free and TPS is still low, the bottleneck is the CPU and the fix is reducing the work per tick.

How do I make my Minecraft server high performance?

Run Paper (or Lithium on Fabric), pre-generate the world, keep simulation distance sensible, profile with spark when TPS drops, and host on a fast single-core CPU with SSD storage.

Should I restart the server regularly?

A daily restart is a cheap way to clear slow memory growth from plugins or mods. It doesn’t fix a farm that lags the server the moment someone stands near it.

Why is my observer not working on a server?

If observers and other redstone behave on single player but not on the server, check TPS first: at low TPS redstone runs slowly. Plugins that limit redstone can also change how contraptions behave.

Skip the 3am debugging

On GameTeam’s Minecraft server hosting, the server runs on Ryzen 9 7950X CPUs with NVMe storage, which covers the single-core speed and fast chunk loading Minecraft wants. When something does go wrong, the AI Crash Analyzer reads latest.log and the crash report and names the exact mod or setting behind it, with the fix. Ask “the server’s lagging near spawn, find out why and fix it” and the AI copilot checks tick times and the log, tells you what’s eating the ticks, lowers the simulation distance if that’s the problem, and restarts the server. It also warns you about RAM before players feel it. The copilot is included on every plan; pay per GB of RAM from $0.49/GB a week, unlimited slots. Running your own? Size it with the RAM guide, revisit how to make a Minecraft server for the basics, or hand the tuning to Minecraft server hosting.

Total
0
Shares
Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts
Cookie Settings