Sometimes when placing a block as far away as possible, it will flicker into existence for a brief moment and then disappear again. This affects survival and creative. In survival the item pops back into your inventory.
To reproduce the problem, load the attached world and, without moving, place the anvil you are holding against the block you are looking at (the first stone block above the portal).
The bug first appeared in 1.3.
Linked issues
is duplicated by 3
Attachments
Comments 16
confirmed. 1.5.2 both vanilla and bukkit server no plugins SP/MP any game mode
http://www.youtube.com/watch?v=rd9DECFqwNk
Also now it also drops items from them glitching out on the placement. Example Ive had a random # stack drop of xp potions after the placed block dissapeared (no I cant say which block as its kinda a serious exploit in the game mechanics).
No problem. I am just going through around 3,800 tickets, and try to sort out those that are completely orphaned.
Btw cant add any 1.7.x versions. The problem seems to stop @ 1.8 as destroy and placement block distances changes from 1.7.10 to 1.8. Not sure if this 'solved' the problem or just started to 'mask' it, as I cant repo it on 1.8. or 1.8.1-pre2 the distance from placing a block vs destroying one is not the same anymore. I cant place blocks @ the same distance as the farthest point that I can destroy one now. Offsetting placement about .05m in distance seems to have changed it all, atleast for me. When the server bugged out on block removal or placement, it was always happening when I was placing blocks at the edge of the highlighted range.
I have to agree with @Sycholic about passing the buck. Saying "Nobody has re-confirmed this in the last 2 years, therefore it's invalid" is just sticking your head in the sand (and by "you" I mean Mojang).
"Pending information" or similar would be a valid status, but only if there's someone at Mojang whose job it is to confirm bugs. Otherwise, it's just another way to disown responsibility.
TL;DR: Getting bugs fixed once they are reported is Mojang's responsibility. If I am expected to help Mojang, then I expect to be paid for my time, like everyone else working for Mojang.
Let's analyze the "Incomplete" message I give out:
This ticket is incomplete without the requested information, no response has been received within a reasonable time and we are assuming this is no longer an issue. If you are still experiencing this issue, we can reopen it at your request.
"we are assuming this is no longer an issue" = Can be either seen as "this has been Fixed in a random version" or "this was once an issue of some sorts, but it is handled as something intended now".
"we can reopen it at your request." = We are actually serious with this, for my part, I am getting E-Mail for every response to a ticket I closed as Incomplete, and therefor I can see if someone comments on it.
I agree that this is a farily new method, but at the current state, the bug tracker as a whole seems a bit unorganized. I've seen quite a few duplicates that were not detected as one. My plan for the future is to do this every big update, and what I am expecting at least from anyone reporting a bug is that he checks it in every big release (next one would be 1.9). Just reporting a bug and thinking that everything would resolve around it completely automatical is not enough.
All bug tracker moderators are volunteers by the way.
Can confirm this bug. I've seen this happen before 1.3