I have also observed this with slabs and stairs in 14w08a. But with an odd twist, in my testing it happens with the wood blocks, sandstone, and stone brick, but it does not happen with nether brick, quartz, cobblestone, red bricks.
I also see the flipped texture under wood fences but not cobble/mossy walls.
Still present in 14w21a, I attached another screenshot showing that normal crystal formations will still occasionally generate, but most of them are missing their bottom layers.
You don't have to specifically place a torch under something, any time you place a torch against an invalid block (like another torch, or cobweb), the torch will try to place against an adjacent block (which it is supposed to do) but the metadata doesn't get set properly so the torch appears in the wrong orientation and will drop if it gets a block update.
Despite the similarities between stems and fire (both include an x pattern) they do in fact use different renderers, so if it is the same bug it appears in at least two different places.
Jason MacWilliams
MC-49126![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
2014-05-22_12.18.50.png
I have also observed this with slabs and stairs in 14w08a. But with an odd twist, in my testing it happens with the wood blocks, sandstone, and stone brick, but it does not happen with nether brick, quartz, cobblestone, red bricks.
I also see the flipped texture under wood fences but not cobble/mossy walls.
Showing the new (flat) generation with the original generation off to the right side.
Shows new (flat) glowstone generation as well as normal generation on the far right
Still present in 14w21a, I attached another screenshot showing that normal crystal formations will still occasionally generate, but most of them are missing their bottom layers.
throwing the dragon egg on the ground still shows the rendering error
You don't have to specifically place a torch under something, any time you place a torch against an invalid block (like another torch, or cobweb), the torch will try to place against an adjacent block (which it is supposed to do) but the metadata doesn't get set properly so the torch appears in the wrong orientation and will drop if it gets a block update.
Despite the similarities between stems and fire (both include an x pattern) they do in fact use different renderers, so if it is the same bug it appears in at least two different places.
If you use an NBT explorer you should see the broken seeds dropping with a damage value of 2 when it should be 0.