The Bug:
Light levels in the F3 debug menu aren't accurate when standing on soul sand.
Steps to Reproduce:
Enable the F3 debug menu and place down some soul sand.
Stand on top of the soul sand and pay close attention to what the game states your light levels are.
Take note as to whether or not light levels in the F3 debug menu aren't accurate when standing on soul sand.
Observed Behavior:
Light levels always appear as "0" when standing on soul sand.
Expected Behavior:
Light levels would be accurate when standing on soul sand.
Related issues
is duplicated by
relates to
Attachments
Comments
migrated
RedCMD
Has this issue been fixed yet?
Cause now we cant place rails, pressure plates, redstone related blocks and many other blocks on it now?
The fact that soul sand is dark and standing on it makes the sky go black, should stay
So WAI?
pokechu22
The sky going black thing was actually fixed a while back (MC-51150); my motivation for creating this issue was MC-46667 being fixed for all blocks other than soul sand. It is still an issue from my testing.
The redstone and rails thing (MC-139497) is presumably its own issue since it's new (as far as I can tell), although it might actually be related to them attempting to fix this by changing whether a face is solid or something (I'd have to investigate further).
(That said, it could very much be WAI, as MC-46667 was marked as WAI (albeit by another mod and not a dev); I'm hoping to get a dev confirmation with regards to that on this issue)
muzikbike
Affects 18w47b
muzikbike
Affects 18w48a
muzikbike
Affects 18w48b, can I request ownership of the ticket?
muzikbike
Affects 18w49a
muzikbike
Affects 18w50a
muzikbike
Affects 19w13b, can I request ownership?
muzikbike
Affects 19w14a
muzikbike
Affects 19w14b
migrated
This also causes mobs like creepers to spawn on soul sand, which can be dangerous if you have a nether wart garden in your base.
Affects 1.14.4 Pre-release 1
AuroraRainbow
Confirmed in 1.14.4, Light Level is 0 and Mobs can spawn because of that
migrated
Affects 21w18a
ampolive
Can confirm in 1.17.1.
migrated
Affects 21w40a
Avoma
Can confirm in 1.18.1.
Avoma
Can confirm in 1.18.2.
Avoma
Can confirm in 21w11a. Closely relates to MC-249227.
tzql1104048
The bug also affects certain mud blocks in mangrove swamp.It still exists in current version(1.19 pre-release 1).
[media][media]
ampolive
Mud blocks are tracked separately in MC-249227.
tzql1104048
Affects 1.19 pre-release 5.
Avoma
Can confirm in 1.19.1.
Avoma
Can confirm in 1.19.2.
Dzekin
Should be closed as WAI.
This is not a bug since by the game's logic you're actually one block lower - it's just a side effect of how mud, snow layers, soul sand have a different hitbox and a different collision box (which can be seen in the provided screenshots - look at Y values)
migrated
Should be closed as WAI.
This is not a bug since by the game's logic you're actually one block lower - it's just a side effect of how mud, snow layers, soul sand have a different hitbox and a different collision box (which can be seen in the provided screenshots - look at Y values)
The problem is if this incorrect light value enables mobs to spawn on the block when they shouldn't. Which according to one comment in the thread it does.
While in a sense the code is working correctly it can hardly be the intended function since it means that it is impossible to light up and spawn proof these kinds of block without physically blocking spawning.
migrated
Can anyone actually verify the mob spawning, because I can't; if a mob would be spawned, it'd have to spawn inside the block, but no mobs can spawn inside solid blocks.
Former user
Mobs do not spawn in soul sands so it doesn't affect mob spawning.
This is not WAI because it leads to render issues like MC-248286, and a priority has already been assigned by Mojang.
In fact, its easy to fix because directional opacity has already been introduced with the fix of MC-46667, so its possible to make soul sand transparent on its top face and opaque on the other five faces.
AMGAMES04
Can confirm in 24w03b