MC-57172/setblock causing ghost blocks?
So I'm setting a block in the air, but when I break it - if there is no block connected to it then it turns into a ghost block. The texture stays, but the bounding box has gone and F3 shows nothing.
Relogging gets rid of it.
If you place blocks next to it, it kind of works like a chain - the last block in the chain to be removed does the ghosting.
Theres no way of actually removing it, without relogging.
How to duplicate:
Run /setblock ~ 64 ~ stone
and built off it with blocks, then break the blocks and the last one will ghost
Not 100% chance, but happens a lot of the time. I'd say 85%
Environment
Mac OS X - Latest Java
Created Issue:
/setblock causing ghost blocks?
So I'm setting a block in the air, but when I break it - if there is no block connected to it then it turns into a ghost block. The texture stays, but the bounding box has gone and F3 shows nothing.
Relogging gets rid of it.
If you place blocks next to it, it kind of works like a chain - the last block in the chain to be removed does the ghosting.
Theres no way of actually removing it, without relogging.
How to duplicate:
Run /setblock ~ 64 ~ stone
and built off it with blocks, then break the blocks and the last one will ghostNot 100% chance, but happens a lot of the time. I'd say 85%
Environment
Mac OS X - Latest Java
So I'm setting a block in the air, but when I break it - if there is no block connected to it then it turns into a ghost block. The texture stays, but the bounding box has gone and F3 shows nothing.
Relogging gets rid of it.
If you place blocks next to it, it kind of works like a chain - the last block in the chain to be removed does the ghosting.
Theres no way of actually removing it, without relogging.
How to duplicate:
Run /setblock ~ 64 ~ stone
and built off it with blocks, then break the blocks and the last one will ghostNot 100% chance, but happens a lot of the time. I'd say 85%
I have also noticed this bug with single blocks, although it only happens about 50% of the time.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.