This is a bug or rather a design flaw that has been in the game forever, the basic is that if you place anything over a slab that is in the bottom position blocks will float over them you can see the screenshots bellow for a visual of what this looks like, to achieve this flaw you need to first place slab in the bottom position meaning that when you stand on the slab you will be exactly .5 unit from the next Y unit for example if you are on a slab that is placed on a Y level of 4 and you stand on it your Y level will be 4.5 as that is .5 unit from the Y level 5.
List of all blocks that are affected by this flaw (works with any variation of the specified block)
Full block (ex: stone, obsidian, pumpkin)
Fence
Fence Gate
Wall
Stair
Cobweb
End Rod
Trapdoor
Iron Bar
Glass Pane
Chest
Daylight Detector
Hopper
Conduit
Bed
Head
Flower Pot
Banner
Anvil
Enchanting Table
Cauldron
Brewing Stand
The only block that are not affected are slabs (both slabs must be the same variation)
Expectations are that the blocks would be on top of the slab even when it is in the bottom position this flaw does not occur on other type of blocks such a torch, button, lantern and many more as those can't be placed on top of bottom slabs but would be expected to work as well example rails on top of a bottom slab and then you would still be able to ride on them, i know this is a old flaw that has been in the game forever and some might think that this works as it should or is not worth to spend the time fixing it but i think otherwise, at the end of the day they made block waterloggable so i see no reason why they could not make block slabbable thats it for me. jeb pls fix 🙂
Attachments
Comments 2
"This is a bug or rather a design flaw"
Exactly opposite. Due to the way the game's block system is designed, having (full) blocks at half-block offset (in this particular context) would be practically impossible. It could lead, at some point, to the need to have an extra block (or more) stored somewhere, and also many algorithms become a lot more complex (and slower).
As annoying as it is, it is not a bug. Not even a design flaw, just a bad side of the chosen method of handling and storing blocks, and the block size.
Thus, this is more like a huge (and I mean HUGE) feature request.
I dont think this can be fixed without completely changing how blocks work, which probably wont happen