Broken blocks don't drop / blocks regenerate / actions don't register — is this lag?

If you break a block and it pops back into place, or your actions simply don't register, you're almost certainly looking at a performance problem rather than a broken world. This is a classic low-TPS symptom, and this guide explains what's happening and how to fix it.

Why blocks "come back"

Minecraft aims for 20 TPS (ticks per second). When the server falls badly behind — low TPS / high MSPT — it can't process your actions in time, so it rejects or rolls them back. The block you broke reappears because the server never registered the change. It means the server can't keep up.

An over-aggressive anti-cheat plugin can occasionally cause the same rollback effect, so keep that in mind too.

How to diagnose and fix it

1. Run a spark report to see where the time is going. Install the spark plugin/mod and use its profiler.
2. Pre-generate your world so the server isn't creating chunks on the fly.
3. Lower view-distance (and simulation-distance) in server.properties.
4. Trim heavy content — redstone contraptions, mob farms, and excessive entities all cost TPS.
5. Upgrade CPU/RAM if the server is genuinely maxed out (raise Xmx on the Settings page or move to a larger plan).
6. Check your anti-cheat config — if TPS is healthy, an anti-cheat may be reverting legitimate actions.

Tip: A spark report tells you whether it's truly a hardware limit or one heavy plugin/mod. Fix the biggest offender first.

Frequently asked questions

How do I know if it's lag or anti-cheat? If a spark report shows healthy TPS, suspect anti-cheat. If TPS is low, it's performance.

Will more RAM alone fix it? Not always — Minecraft is CPU-bound. RAM helps if you're out of memory, but CPU and world optimization often matter more.

Where do I read more? See our performance and lag articles for pre-generation, view-distance tuning, and plan sizing.