Sometimes you can found (on oasis in the desserts) some floating sand and if you broke one of blocks that this floating sand touches, the sand will fall down.
Linked issues
is duplicated by 24
relates to 3
Attachments
Comments 15
Honestly I think this should be left as-is. It brings another level of caution and danger to the game. Yesterday I was exploring in a desert, when my friend popped a block. An entire hillside came down right next to me. Luckily I wasn't directly underneath, but it definitely got my heart beating.
I've seen this happen too, and I wish it were fixed. Alternately, if there were some way for the player to produce the same structure, that would be neat. I don't like that the generated world contains things the player couldn't create.
It's certainly a feature and not a bug. Floating sand has been in the game since forever, and there even are special particles just for floating gravity blocks.
Careful with the terms.. In this particular case, it belongs to the category of being a bug that is (was) accepted (by Mojang) as (more or less) permanent feature. (An issue can be both, a bug, and a feature, i.e "Won't Fix".) Note also the use of quotes around the word "feature" in earlier comment by Nathan Adams. (It was certainly nice that those particles have been added there, giving a warning about its volatile nature.)
(The part of "been in the game since forever" is one of the common, yet very bad reasons for stating something is not a bug. Been in the game for long might indicate, or at least correlate, on it being a feature (or at least accepted as "wont fix"/"feature"), but... For example, see MC-7200. It is a very obvious bug (incorrect math), been there for around 9 years.)
Btw. my earlier comment about noting to see Dinnerbone's comment (in MC-610).. no idea, I couldn't myself find such any more. However, Nathan Adams once upon a time (2013) resolved it by using state "Won't fix", which implies it being a bug, but just accepted to stay as a "feature"...
... Until years later, Mojang decided to reopen it (meaning they have intent to work at least on some part of it), with priority "important". Does not sound to me like it being a fully accepted "feature" at that point. The problem is, as usual with Mojang, they don't bother much with looking at linked issues, and end up resolving them in different ways. (Or not resolving at all, compare MC-7196 and MC-7200 case, frigging same classes, even same methods, fixes provided, issues linked, and they fix just the other one ><). MC-610 was marked "Won't fix", this one "Working as intended", even though it was clear that both should have been handled the same. And later, MC-610 was reopened, this one was not.
Note, the generic root cause for most of these floating stuff -related issues are sort of same, even if the technical mechanism might have slightly different ways in leaving the floating something in the world. Thus, I'd assume that if Mojang considers one floating weird to be worthy of fixing, they might consider all of them... if they just remembered to look at the linked issues.
The particles emitted by sand are proof enough for me that this is fully intended by now.
For any further discussion, please use our Subreddit or Discord Server
It has been that way a very long time. I don't consider it a problem