When placing a wall using /setblock without specifying a block state, it is invisible; default state has up=false
The bug
When you run /setblock ~2 ~ ~ minecraft:cobblestone_wall an invisible cobblestone wall will be set (aka, every single block state is false). I would have expected the wall to have the block state up=true, so it is visible.
To reproduce
- Run /setblock ~2 ~ ~ minecraft:cobblestone_wall
- Apparently, nothing happens
- Run /setblock ~2 ~ ~1 cobblestone
- Now, the wall appears.
Linked Issues
is duplicated by2
Created Issue:
When placing a wall using /setblock without specifying a block state, it is invisible
The bug
When you run /setblock ~2 ~ ~ minecraft:cobblestone_wall an invisible cobblestone wall will be set (aka, every single block state is false). I would have expected the wall to have the block state up=true, so it is visible.
To reproduce
- Run /setblock ~2 ~ ~ minecraft:cobblestone_wall
- Apparently, nothing happens
- Run /setblock ~2 ~ ~1 cobblestone
- Now, the wall appears.
When placing a wall using /setblock without specifying a block state, it is invisible; default state has up=false
is duplicated by
relates to
is duplicated by
relates to
relates to
relates to
relates to
relates to
The bug
After upgrading, glass panes, fences, iron bars and cobblestone walls which were previously connected to blocks are no longer connected.
Examples
- Fences
/tp @s -106.72 85.00 449.47 -431.18 3.55
- Iron bars
/tp @s -110.71 68.00 451.82 70.01 8.92
- Cobblestone walls (invisible due to
MC-127116)/tp @s -95.32 66.00 455.91 450.00 5.24
Resolving as duplicate of MC-127116, the issue is that the default state has all connections (including "up") set to false; blocks filled next to each other update the approopriate connection state only; and since the top wall gets no update from above, it stays with all connections set to false.
Relates to MC-127116.