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.
Related issues
is duplicated by
MC-5485
Sand doesn't fall on some hills
MC-10035
Sand doesn't update
MC-19264
Sand doesn't drop in water!
MC-40956
Floating sand
MC-56423
New Desert Caves causing random above ground structures
MC-58944
Sand dose not fall??????
MC-68669
Sand in newly generated chunks not affected by gravity
MC-77771
Floating sand bug :P
MC-80286
Cavern leaves piece of ocean floor unsupported
MC-84635
Blocks of sand when generating world, floats into the sky and do not fall.
MC-96631
Floating blocks that are supposed to fall generated in chunks
MC-108570
floating sand and gravel genorated
MC-156492
naturaly generated sand problem
MC-172487
Gravel floating in the air
MC-220466
Floating sand will randomly generate upon spawning in a desert biome
MC-220647
Red sand left hanging in air when cave carved beneath
MC-233639
Sands and gravels can stay in the air as long as there is no player influence on the world formation
MC-239372
Floating Gravel with Dripstone
MC-259907
Generated sand doesn't fall when having no blocks under it
MC-267823
bugs in generation
MC-279172
Spring feature spawns around invalid blocks
MC-279607
The sand sometimes hangs in the air
MC-297850
Floating blocks
MC-298376
Floating sand and gravel
relates to
Attachments
Comments
migrated
It has been that way a very long time. I don't consider it a problem
Yeah, but maybe finaly it will be fixed _
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.
Not really a bug, and like Talven said I'm rather fond of this specific "bug".
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.
Nathan Adams
This is a "feature" of world generation.
Would be damn hard to fix and probably slow the world generation down to 10 min per chunk 🙂
I don't think this bug should be fixed, as it looks kinda cool.
bugi74
This issue, MC-5485 and MC-1340 are likely duplicates of MC-610; there is a lake underneath in each issue. The remaining two issues seem to have different cause. Since dinnerbone has stated in this issue that it is a "feature", might be reasonable to resolve MC-610 the same (and hint about the reason being in this issue).
Then again, the MC-610's detail (grass/flowers/etc) can have easy workaround (just check one more block above and remove as necessary), so maybe keep it open until decided by Mojang.
i can confirm this bug!
bugi74
And Mojang has confirmed that while it is a bug, they have decided it will stay, thus this (and some other related ones) are resolved as "works as intended" or the more correct "won't fix". See MC-610, Dinnerbone's comment.
FaRo1
This has to have state "Won't fix", not "Works as intended".
That's right. WAI does not make any sense.
violine1101
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.
bugi74
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.
NeunEinser
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