Ghost blocks remain when insta-mining; reappearance of MC-5694
The bug
Insta-mining blocks (e.g. dirt with an efficiency 5 diamond shovel) occasionally leaves behind ghost blocks, of which there still is a server-side hitbox but the client counts it as already dug.
This happens quite often - just going around like this produces one mismatched block every few seconds.
As I cannot reproduce this in any pre-release prior to pre4 (so I can from pre4 and upwards), I believe this is related to the new packet/fix for MC-156013.
How to reproduce
See the attached video, reproducing the bug in a freshly created singleplayer world (I also waited for generation to calm down before starting to dig).
Linked Issues
is duplicated by38
MC-156832Ghost blocks appear againDuplicateMC-156904when you destroy sand there would be invisible floating sand that blocks you from walking and you can stand on it and if you place a block under it that block will become sandDuplicateMC-157130Invisiable Walk Through Blocks in the NetherDuplicateMC-157239Ghost blocks are backDuplicateMC-157253StuckDuplicateMC-157332Invisible blocksDuplicateMC-157369The ghost blocks returnDuplicateMC-157384Ghost Block DuplicateMC-157408Breaking blocks creates ghost blocksDuplicateMC-157416Invisible blocks when mining at normal speedDuplicateMC-157449Ghost BlocksDuplicateMC-157531Ghost Sand BlocksDuplicateMC-157632Invisible BlocksDuplicateMC-157811blocks acting as if they have not been destroyedDuplicateMC-157890After breaking blocks in vanilla 1.14.4 minecraft invisible "things" (not full blocks) stop the playerDuplicateMC-158000Invisible blocksDuplicateMC-158106invisible walls created by digging too fast in survival modeDuplicateMC-158109ghost blocksDuplicateMC-158420Ghost dirt blocks at around level Y11DuplicateMC-158543Instant Mining Causes Invisible/Glitched BlocksDuplicateMC-158591Invisible Blocks Blocking My Path when I mine with an efficiency 5 diamond pick and a haste 2 beacon.DuplicateMC-158882invisible dirt blocks if mined too fastDuplicateMC-158958When I mine to fast "ghost blocks" generates.DuplicateMC-159023Blocks mined glitching and trapping avatarDuplicateMC-1590681.14 Ghost Blocks When Mining FastDuplicateMC-159078Haste II + Efficiency V Invisible Blocks Glitch DuplicateMC-159127Mining a lot of blocks fast sometimes create invisible blocksDuplicateMC-159244Ghost blocks made from insta-mining blocks are backDuplicateMC-159282Cuando rompo un bloque con un pico o pala de diamante con eficiencia 5 Quedas flotandoDuplicateMC-159384Breaking Blocks Too Quickly Causes Block to not Update ProperlyDuplicateMC-159889invisible wall stopping me from movingDuplicateMC-160183Block Appears To Break But Dosen'tDuplicateMC-160937Invisible blocks blocking the way DuplicateMC-161016Ghost Blocks in IceDuplicateMC-162311Player Floats in SurvivalDuplicateMC-163527Player glitches when using a super powerful and fast pickaxeDuplicateMC-164636Invisible blocks when mining fastDuplicateMC-164829Invisible blocksDuplicate
NormalAttachments1
![[Mod] Nassim Jahnke](../../../data/avatars/users/94205.png){kind=small}
Created Issue:
Ghost blocks remain when insta-mining
Insta mining blocks (e.g. dirt with an efficiency 5 diamond shovel) occasionally leaves behind ghost blocks, of which there still is a serverside hitbox but the client counts it as already digged.
This happens quite often - just going around like this produces one mismatched block every few seconds.As I cannot reproduce this in any pre-release prior to pre4 (so I can in 4, 5, and 6), I believe this is related to the new packet/fix for https://bugs.mojang.com/browse/MC-156013
See the attached video.
Insta mining blocks (e.g. dirt with an efficiency 5 diamond shovel) occasionally leaves behind ghost blocks, of which there still is a serverside hitbox but the client counts it as already digged.
This happens quite often - just going around like this produces one mismatched block every few seconds.As I cannot reproduce this in any pre-release prior to pre4 (so I can in 4, 5, and 6), I believe this is related to the new packet/fix for https://bugs.mojang.com/browse/MC-156013
See the attached video.
Insta mining blocks (e.g. dirt with an efficiency 5 diamond shovel) occasionally leaves behind ghost blocks, of which there still is a serverside hitbox but the client counts it as already digged.
This happens quite often - just going around like this produces one mismatched block every few seconds.As I cannot reproduce this in any pre-release prior to pre4 (so I can in 4, 5, and 6), I believe this is related to the new packet/fix for https://bugs.mojang.com/browse/MC-156013
See the attached video, reproducing the bug in a freshly created singleplayer world (I also waited for generation to calm down before starting to dig).
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
Insta mining blocks (e.g. dirt with an efficiency 5 diamond shovel) occasionally leaves behind ghost blocks, of which there still is a serverside hitbox but the client counts it as already digged.
This happens quite often - just going around like this produces one mismatched block every few seconds.As I cannot reproduce this in any pre-release prior to pre4 (so I can
in 4, 5, and 6), I believe this is related to the new packet/fix for https://bugs.mojang.com/browse/MC-156013See the attached video, reproducing the bug in a freshly created singleplayer world (I also waited for generation to calm down before starting to dig).
Insta mining blocks (e.g. dirt with an efficiency 5 diamond shovel) occasionally leaves behind ghost blocks, of which there still is a serverside hitbox but the client counts it as already digged.
This happens quite often - just going around like this produces one mismatched block every few seconds.As I cannot reproduce this in any pre-release prior to pre4 (so I can from pre4 and upwards), I believe this is related to the new packet/fix for https://bugs.mojang.com/browse/MC-156013
See the attached video, reproducing the bug in a freshly created singleplayer world (I also waited for generation to calm down before starting to dig).
Insta
mining blocks (e.g. dirt with an efficiency 5 diamond shovel) occasionally leaves behind ghost blocks, of which there still is a serverside hitbox but the client counts it as already digged.
This happens quite often - just going around like this produces one mismatched block every few seconds.As I cannot reproduce this in any pre-release prior to pre4 (so I can from pre4 and upwards), I believe this is related to the new packet/fix for
https://bugs.mojang.com/browse/MC-156013See the attached video, reproducing the bug in a freshly created singleplayer world (I also waited for generation to calm down before starting to dig).
The bug
Insta-mining blocks (e.g. dirt with an efficiency 5 diamond shovel) occasionally leaves behind ghost blocks, of which there still is a server-side hitbox but the client counts it as already dug.
This happens quite often - just going around like this produces one mismatched block every few seconds.As I cannot reproduce this in any pre-release prior to pre4 (so I can from pre4 and upwards), I believe this is related to the new packet/fix for
MC-156013.How to reproduce
See the attached video, reproducing the bug in a freshly created singleplayer world (I also waited for generation to calm down before starting to dig).
is duplicated by
Ghost blocks remain when insta-mining; reappearance of MC-5694
relates to
is duplicated by
is duplicated by
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
Very Important![[Mojang] Georgii Gavrichev](../../../data/avatars/users/22428.png){kind=small}
[Mojang] Georgii Gavrichevis duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
is duplicated by
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
relates to
is cloned by
clones
Please reopen, I can't play when this happens to me every 5 minutes. It has gotten better, but I still blame Xisuma for them reintroducing the bug.
![[Mod] Les3awe](../../../data/avatars/users/79847.png){kind=small}
relates to
The bug
When spam-clicking with the sword on the ground and run at the same time the character gets stuck.
This also happens when left clicking with the debug stick in Creative mode and when hitting blocks which can normally be broken instantaneously in Survival with a debug stick.
How to reproduce
- Be in gamemode creative
- Get a sword or a trident
- Look at the ground and spamclick on the left mouse button
- Try to run while you still spamclick with your sword/trident
Further notes by VeilStar
This issue affects more than what is currently mentioned in here.
Any time the player (attemps to) break a block, but the block isn't broken server-side, the player gets teleported back to where they were when they broke that block.
This issue appears when running around while clicking the ground with a sword in creative mode I assume because the client is actually still sending 'block interaction packets' as they are technically still 'mining' the block. However, neither the client nor server break the block because the player is holding a sword.
This same issue can also be observed in survival mode when the server is lagging as the lag introduces 'block lag'. Block lag is when the player mines a block but the block re-appears due to not (yet) being broken server-side because of the lag. Before this issue was introduced the block re-appeared and that was that. Since this issue was introduced the player also gets teleported back as soon as the block re-appears. (Here's a video showing this on a vanilla singleplayer world where I caused excessive server lag for the purpose of demonstration.)
Also, while I know this isn't relevant for you guys, this issue also affects modded servers where the player isn't allowed to break certain blocks or blocks in certain areas. The block gets broken client-side, but then re-appears for the client in the next (server) tick, and since 1.14.4 (Pre-Release 4?) the player gets teleported back to the location they were at when they broke the block client-side. (Here's a video of that on a spigot 1.14.4 server with a plugin that offers such functionality.)
This is almost certainly caused by the fix for
MC-156013, andMC-156852might be in the same boat. What is the point of pre-releases anymore if changes introduced in them cause more issues than they solve and make it into the final releases for a version? Anyhow, my point is that fix implemented forMC-156013is plain bad and I can't trust you guys to not fix this issue by doing something equally bad, like adding a check that doesn't teleport the player back if they're holding a sword.With that said, a better fix for
MC-156013using the current method is probably to teleport the player back only if the player's hitbox intersects the re-appearing block. This would get rid of this issue as well.
This issue affects more than what is currently mentioned in here.
Any time the player (attemps to) break a block, but the block isn't broken server-side, the player gets teleported back to where they were when they broke that block.
This issue appears when running around while clicking the ground with a sword in creative mode I assume because the client is actually still sending 'block interaction packets' as they are technically still 'mining' the block. However, neither the client nor server break the block because the player is holding a sword.
This same issue can also be observed in survival mode when the server is lagging as the lag introduces 'block lag'. Block lag is when the player mines a block but the block re-appears due to not (yet) being broken server-side because of the lag. Before this issue was introduced the block re-appeared and that was that. Since this issue was introduced the player also gets teleported back as soon as the block re-appears. (Here's a video showing this on a vanilla singleplayer world where I caused excessive server lag for the purpose of demonstration.)
Also, while I know this isn't relevant for you guys, this issue also affects modded servers where the player isn't allowed to break certain blocks or blocks in certain areas. The block gets broken client-side, but then re-appears for the client in the next (server) tick, and since 1.14.4 (Pre-Release 4?) the player gets teleported back to the location they were at when they broke the block client-side. (Here's a video of that on a spigot 1.14.4 server with a plugin that offers such functionality.)
This is almost certainly caused by the fix for MC-156013, and MC-156852 might be in the same boat. What is the point of pre-releases anymore if changes introduced in them cause more issues than they solve and make it into the final releases for a version? Anyhow, my point is that fix implemented for MC-156013 is plain bad and I can't trust you guys to not fix this issue by doing something equally bad, like adding a check that doesn't teleport the player back if they're holding a sword.
With that said, a better fix for MC-156013 using the current method is probably to teleport the player back only if the player's hitbox intersects the re-appearing block. This would get rid of this issue as well.
This issue duplicates MC-156852.
If you have any additional information, we would appreciate you adding it to that report. If you have not already, please use the search function to see if your issue has already been reported.
This issue duplicates MC-156852.
If you have not already, please use the search function to see if your issue has already been reported.
Please see MC-156852 if you have this issue in 1.14.4.
Duplicate of MC-156852.
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket 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 in the future to see if the issue has already been reported.
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket 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 in the future to see if the issue has already been reported.
Does MC-156852 describe your issue?
No, MC-156852 does not describe my issue. No ghost blocks are left behind, but my player is teleported to a previous position and my view controls get teleported to a previous position as well.
Duplicate of MC-156852.
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket 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 in the future to see if the issue has already been reported.
This issue duplicates MC-156852.
If you have not already, please use the search function to see if your issue has already been reported.
This issue duplicates MC-156852.
If you have not already, please use the search function to see if your issue has already been reported.
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket 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 in the future to see if the issue has already been reported.
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved. Depending on the resolution, that can mean that it either will be fixed in the next version, or that it is not considered a bug and won't be fixed.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Duplicate of MC-156852. Please note that bug reports are only accepted in English.
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved. Depending on the resolution, that can mean that it either will be fixed in the next version, or that it is not considered a bug and won't be fixed.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved. Depending on the resolution, that can mean that it either will be fixed in the next version, or that it is not considered a bug and won't be fixed.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved. Depending on the resolution, that can mean that it either will be fixed in the next version, or that it is not considered a bug and won't be fixed.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved. Depending on the resolution, that can mean that it either will be fixed in the next version, or that it is not considered a bug and won't be fixed.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved as Fixed, meaning that it is a known issue that has already been fixed.
The fix will arrive in the next version or is already included in the latest development version of the game.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved as Fixed. The fix will arrive in the next version or is already included in the latest development version of the game.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved as Fixed. The fix will arrive in the next version or is already included in the latest development version of the game.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved as Fixed. The fix will arrive in the next version or is already included in the latest development version of the game.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
MC-156852 is resolved in 19w34a, which is a Minecraft 1.15 snapshot.
Thank you for your report!
We're actually already tracking this issue in MC-156852, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved as Fixed. The fix will arrive in the next version or is already included in the latest development version of the game.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
Thank you for your report!
We're already tracking this issue at MC-156852, so I will resolve and link this ticket 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:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
Both this issue and a clone of it (MC-156852) have been resolved as fixed, in 17w50a and 19w34a respectively. If you're still experiencing it, create a new issue, with updated steps to reproduce, please.
This has been a bug in the game for as long as I can remember. Happens also when using a Eff 5 pick with Haste 2 on stone type blocks
That's probably another cause, then. I cannot reproduce the cause/issue I'm referring to in pre3, so this in particular should be a new one.
Can confirm this is in 1.14.4 as well. Yesterday (1.14.3) I was clearing a large area of dirt with an Efficiency V Diamond shovel and didn't have any problems. Just now after updating to 1.14.4, I'm clearing the same area with the same shovel and every 15 blocks or so I get stuck in a ghost block and have to log out and back in to get out of it. This was definitely not in 1.14.3. I should also mention, this is on a server.
Can confirm on 1.14.4 paper.
Bugs should be tested on vanilla servers and clients, just to note.
(Though yes, it's been tested on both of those)
Can confirm, happens every time i insta mine to ~1 in 20 blocks.
To add: (in singleplayer at least)
The 'ghost blocks' get replaced by actual blocks when relogging.
Placing a block where the 'ghost blocks' are will consume the held block and place the block that used to be there instead
Can be triggered by instamining individual blocks.
Items are not dropped when a block becomes a 'ghost block'
I started to get this bug in the nether in 1.14.4.pr6. Never had it before that.
Can confirm on 1.14.4 vanilla. Didn't happen on 1.14.3
Can confirm for finished Version 1.14.4: possibily for any stone block mined with an diamndpickaxe with efficiency 5 and the Haste 2 effect from a beacon.
Also chiming in to confirm I'm seeing this on 1.14.4 where-as it was previously resolved.
Would hate to see another 1.14 release, but this is worthy of 1.14.5 for sure.
Can also confirm on vanilla 1.14.4. Efficiency 5 pick with haste 2. Very annoying.
Can confirm. 1.14.4 Pick with Efficiency 5 mining ice.
Can confirm this too. Used a Efficiency 5 shovel on dirt.
I found a solution. The patch is here. https://github.com/PaperMC/Paper/pull/2396/files
I used the same fix as
MC-5694.I have only tested this on [Paper | https://papermc.io] but I expect this will work on vanilla Minecraft as well.
Does that fix keep the fix for the "get nudged to the side when mining down a tower while having lag" bug? Slicedlime said that fixing that bug reintroduced this one.
Even if it doesn't ghost block are a lot more annoying and more frequent, I wish we get 1.14.5 just for fixing ghost block.
Mojang prioritised this one. And that bug can cause you to do, this one just annoys you a bit until you reload the world.
Will we have to wait until 1.15 to get a fix?
The latest server version form papermc.io already has this patched. For those of you looking for a fix now.
Again the code fix is here. https://github.com/PaperMC/Paper/pull/2396/files
(Full disclosure, yes I patched it.)
Matt S, I'm curious: Does the fix that you implemented for Paper re-introduce
MC-156013? Have you tested that?Under lag (~100ms) this does seem to re-add
MC-156013. It does not seem to have a problem under normal conditions however.Ghost blocks were accepted knowingly to fix
MC-156013. And I agree with that, I definitely prefer having to relog over potentially falling to my death.I dont agree, i dont pillar up enough times as the times I instamine. I have bad experiences with both, but ghost blocks is the worst offender here.
I rarely have any latency issues, but I can bet than anyone with them would prefer having ghost blocks than to just die when digging down a tower.
... though eitherway, discussing this won't really solve anything, Mojang will have to make a fix that covers both in the next update anyways. 👀
Why are you pillaring anyway when scaffold blocks exist?
Relogging every 15 seconds is infinitely more annoying than dying on the rare time you pillar for whatever reason.
Because bamboo jungles are rare. Anyway, Mojang has decided already which bug is more important.
This issue becomes specially frequent when you lose Haste II. I mean, while you keep Haste II active, you will see this issue only if there's a lag spike, and not always. But you can intentionally reproduce this issue by just going out of range of your beacon while you are mining, and if you keep mining with Haste 2, the mined blocks at Haste 2 goes will be ghost blocks.
Has anyone else experienced the
MC-156013while using a patched version (the current Paper Minecraft)?I did experience issues with mining straight down, but I can't seem to recreate that problem.
Perhaps this is actually a workable solution after all?
Has anybody found a temporary fix for this at all? This is occurring on my 1.14.4 Spigot server and is creating a very frustrating experience.
@Tony - Yeah use Paper instead
Hello,
I have efficiency V on all my tools and I don't play on server, never made a server, I play single player world and this happens all the time because with efficiency V, the dirt blocks especially get mined almost instantly and I end up with tons of ghost blocks, I see that paper servers have a fix for this and the user Mat also posted here a fix but since I play single player world how can I fix this? As it is it's a very frustrating bug that is taking away my enjoyment of the game because I end up getting stuck on ghost blocks every 2 minutes or so when I'm mining and I would like to use efficiency enchantment on my tools...
Which version are you playing in?
I am playing on 1.14.4, single player world
This bug will be fixed in 1.15.
There is another bug in 1.15.1 which is in another form, as in the video below, I place a tile and then I use the following command on the block:
/summon minecraft:falling_block -433 111 -168 {BlockState:{Name:"minecraft:andesite_slab",Properties:{type:top}},Time:-1000000,NoGravity:true}at that time, the block turns into a ghost block that can no longer be broken. Then I delete the falling block and the block is invisible, you have to click on it so that it reappears to break it.
The video : https://youtu.be/7q64k9DMdX8
That's a completely separate issue. Please create a new ticket for it.
This still seems to be an issue, albeit happening more rarely.
→
MC-172550Yall have servers close to you and it shows. Us who dont have any realm server closer than 200ms suffer from this. If it takes falling off pilars I GLADLY take it again. Because I can just not 1block pillar up to take a screenshot, while trying to flatten a hill brings a ton of frustration. Thank you for taking this into consideration.