The Minecraft forums seem to be filled with threads regarding a "block respawn" bug. I set up a 1.3 SMP server on my LAN, and notice this as well. All blocks respawn a couple of seconds after being destroyed, and non-local players lag tremendously.

It makes the game unplayable. Has Notch commented this issue? Is there a solution that makes the game worth buying?

  • This question is very localized in time, it might be closed unless you can reword it to be about Minecraft SMP in general. – Sadly Not Mar 24 '11 at 14:26
  • Double rollback, oh my god. – Sadly Not Mar 24 '11 at 16:32
  • I also had this problem, but I thought it was related to Bukkit, because after upgrading to build526(?) the bug was gone...at least for me, another player was commenting that it was still there...odd... – Bobby Mar 25 '11 at 20:38

How far from spawn are your players? There is a protected area around spawn in which non-op'ed players cannot destroy existing blocks or place new blocks to prevent griefing. Our SMP server has no problems, so I don't think it's a minecraft-wide issue.

| improve this answer | |
  • 5
    I didn't know that! Turns out I was having both issues. This also happened outside of the spawn protection, but only sometimes. Turns out it was caused by regular lag due to loading chunks. If I waited a couple of minutes after a chunk, it would be playable again. – user7220 Mar 24 '11 at 15:33
  • Wanted to add that when this starts happening to me it's usually just after going to a new area. So whenever I do move to a new spot I do a quick disconnect and reconnect to load chunks afresh. – riv_rec Mar 24 '11 at 16:21
  • Comparatively, how slow/fast are the clients and the server you are running? Also is it an internet server, or LAN? – Ape-inago Mar 24 '11 at 23:24

The latest version of the server (as of Minecraft 1.3_01) is using the new region save system. This method means that the server is much more efficient as sending chunk updates to players.

It only happens for us on our LAN with slower computers running.

It may be that the client's handler that receives chunk updates is getting flooded, so never gets around to sending the destroyed block event back to the server. The client spends so much time receiving, that it either throws the update away, or the server flags it as "stale" went it is finally gets there (and ignored).

The server notices that the block really isn't destroyed, so once it gets around to it, it sends a chunk update to the client that lets it know the block really exists from the server's perspective (so it pops back into existence from the clients point of view).

Rejoining the game, or hitting [alt] (which pauses the rendering, so the game has more time to receive), allows the client to catch up. The best cure is to make sure that you stand still just after spawning, at least until all the chunks are loaded on the client. You have to ensure that subsequent chunks aren't bombarded all at once, so using server mods like MyWarps or Worldedit's jumpto can cause the issue.

It is especially bad if a virus-scanner kicks in on the slow client machine, causing the client to repeatedly lag behind even with the smaller amount of chunk updates.

This may have been a problem all along, but because the old files took so long to load, they never swamped the client. The rarity of the problem is easy to explain if Minecraft is running on a server/client queuing system.

| improve this answer | |

The community is aware of this issue. You can find the official bug report thread regarding this on Get Satisfaction. Vote this up in order to have best visibility for a possible fix.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy