Blocks reappearing after breaking
I am playing MC 1.9, in singleplayer without commands. When I break blocks they keep reappearing despite the break animation. My frame rate was low but the problem was still there after I fixed the frame rate. I have tried fixing the frame rate multiple times with no success in fixing the initial problem.
Best Answer
Generally, what is called "block lag" is from the game taxing the hardware being used (your computer in this case) for more RAM. Normally, Minecraft can get away with a fairly small 2 gigabytes of RAM, but with larger modpacks, it's common to increase the assigned RAM limits to 4GB or more.
Pictures about "Blocks reappearing after breaking"
Why when I break a block it reappears?
Basically it means the client is breaking too many blocks too quickly, and when the info is sent to the server it cant process it or its lagging behind, therefor it reappears on the client.How do you fix blocks not breaking in Minecraft?
The answer is simple: if you do /gamemode adventure @a, than none of the players can place or break blocks. Show activity on this post. Just turn Trust Players off. If you cannot, sorry!How do you stop people from breaking blocks?
Initially only a few block types can be feasibly broken using only your hand, including dirt/grass, sand, wood and leaves, so try left-clicking and holding and see if you can break these types of blocks. If nothing is happening when you left click, then your mouse button might not be properly mapped.How to make a block reappear after breaking it (command block tutorial)
More answers regarding blocks reappearing after breaking
Answer 2
This isn't related to framerate. This is related to latency and memory issues. I have the same issue when playing myself with a large modpack like Resonant Rise or a resource pack. Note that the blocks usually eventually do disappear, but you might have to mine them again.
The problem could be related to a lack of memory in Java. You could try and assign more memory. However, I'm not sure if this fixes it.
Sources: Stack Exchange - This article follows the attribution requirements of Stack Exchange and is licensed under CC BY-SA 3.0.
Images: Alexa Popovich, DS stories, Maël BALLAND, Hanna Auramenka