When breaking a block that should be instamined, somewhere at about .1% (very rough estimate) of blocks will immediately reappear after you break them
This doesn't appear to be caused by tick lag.
Linked issues
duplicates 1
Attachments
Comments 5
It doesn't look like the tick lag that you see on servers where it disappears, then reappears, then disappears again without being broken, it disappears for like a split second and reappears and you actually have to break it again. I will attach a video showing it. If it is caused by lag maybe the fact that the desync happens in the first place can be fixed.
MC-858 seems very similar, if not identical to this. There are other similar reports resolved as duplicates of it too.
MC-138550 Also describes this issue.
Thank you for your report!
We're tracking this issue in MC-858, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
This is tick lag, even if not constantly lagging, it desyncs client and server mining progress and the server tells the client "No, the block isn't broken yet". Instana-mining still requires the client and server to agree on the block being mined for long enough. A packet being missed by the server (or late) will as such mean it desyncs.
Reports of lag being present are not accepted unless there's a specific cause you can pinpoint.