mojira.dev
MC-44773

Blocks can not be placed directly in front of you, disappears and you have to move back to place them

I stood in a block, and tried to place a block in same height as my head, just in the block next to me, but the block could not be placed until a moved back!

Comments

migrated

Also effects 14w05b. In addition to not placing a block, the count is still decreased by one. For instance: I have 3 blocks of dirt, I try to place one directly in front of me and it fails but now it shows I have 2 blocks of dirt, I pick up a block of dirt and it says I have 4 blocks of dirt.

galaxy_2alex

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.

migrated

Bug is fixed as far as i can see

ziggurism

I haven't figured out how to get 100% reproducibility, but I see this bug in minecraft 1.8.8 and just saw it in current 1.9 snapshot 15w35e. Cost me a chorus flower.

ziggurism

I'm reproducing this bug more reliably now. You just have to stand right on the edge of the space where you are trying to place a block. If you're in just exactly the right place, when you place block, it makes the block placement sound, flashes for one instant, and then disappears. The block is then gone from your inventory. I've repeated it several times in 16w03a. This is an annoying bug that cost me a block of diamond ore when I was new to the game. I'd love to see it fixed. Which means also that I think this bug report should be reopened.

To reproduce it yourself, just put a block in your hand, try to place where you are standing, and very slowly walk backwards until you're right on the edge of blocking placement. If it places successfully, just walk backwards again and repeat. After the 3rd or 4th try, I am able to exhibit the bug. Sometimes if I stay right there, I can disappear 4 blocks in a row.

Do it in survival mode to see that the disappeared block is also gone from your inventory.

ziggurism

Upon more experimentation watching closely, it seems that when you do step back and successfully place a block, the missing blocks do get readded to your inventory. This makes the bug weirder but perhaps less detrimental to gameplay.

ziggurism

Confirmed for 16w04a. @Galaxy_2Alex, please reopen!

migrated

There's a more recent ticket for this bug, please find that and comment there.

ziggurism

@redstonehelper. I'm sorry, but after searching several variations of "disappearing block" or "place block collision" and others, I did not find a duplicate of this bug. Several about switching inventory slots with number keys (all duplicating MC-2912), some about chunk loading errors causing blocks to disappear. The title of MC-62166 ("Breaking / placing / changing blocks has a delay to disappear / appear") seemed like it might encompass this, but the report was something else entirely. But I found nothing else for this issue, blocks disappearing because they were placed too close to the player's collision mask. Does the newer ticket have a very different title?

migrated

Found it: MC-8471.

ziggurism

Thanks redstonehelper. Yes, that looks like it is the same bug. Sorry for making you do the legwork. Not sure why I couldn't find that. I will put future comments on MC-8471.

migrated

(Unassigned)

Unconfirmed

block, block-placing

Minecraft 14w02c

Minecraft 1.8

Retrieved