Detecting the block states not saved in meta data does not work
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=true
directed at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"
Note: I was told to make an issue separate from MC-109353 even though both bugs seem similar.
Affected blocks
Last updated for 1.11.2
| Blockstates | Properties |
|---|---|
| bed[part=foot] | occupied 1 |
| chorus_plant | north, east, south, west, up, down |
| dirt[variant=podzol], grass, mycelium | snowy |
| wooden_door[half=lower], iron_door[half=lower] | hinge, powered |
| wooden_door[half=upper], iron_door[half=upper] | facing, open |
| all fences | north, east, south, west |
| all fence gates | in_wall |
| fire | north, east, south, west, upper |
| flower_pot | contents |
| iron_bars, glass_pane, stained_glass_pane | north, east, south, west |
| powered_repeater, unpowered_repeater | locked |
| redstone_wire | north, east, south, west |
| all stairs | shape |
| pumpkin_stem, melon_stem | facing |
| tripwire | north, east, south, west |
| vine | up |
| cobblestone_wall | north, east, south, west, up |
1 If the occupied property of the foot part is false, but the head part true
Code analysis
For flower pots, see MC-109353
Linked Issues
is duplicated by5
MC-109353Detecting the block states of flower_pots doesn't workDuplicateMC-109891Observers Can't Detect Redstone Wire's Side ChangeDuplicateMC-110533Changes in melon/pumpkin stems don't get detected by observerDuplicateMC-110895Detecting read-only blockstates always returns falseDuplicateMC-127766Observers not detecting melon stem facing block state changingDuplicate
LowAttachments1
Created Issue:
Detecting the block states of iron_bars, fences and (stained_)glass_panes does not work
When running /testforblock on iron_bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
[code]
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
[/code]
and
[code]
/testforblock ~1 ~ ~ minecraft:iron_bars east=true
[/code]
directed at an iron_bars block with the blockstate east=true,north=false,west=false,south=falseWhat I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the blockstate for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Environment
Windows 10
Java 1.8.0_51 (64 bit)
Attachments1
When running /testforblock on iron_bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
[code]
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
[/code]
and
[code]
/testforblock ~1 ~ ~ minecraft:iron_bars east=true
[/code]
directed at an iron_bars block with the blockstate east=true,north=false,west=false,south=falseWhat I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the blockstate for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
When running /testforblock on iron_bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
[code]
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
[/code]
and[code]
/testforblock ~1 ~ ~ minecraft:iron_bars east=true
[/code]
directed at an iron_bars block with the blockstate east=true,north=false,west=false,south=falseWhat I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the blockstate for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
When running /testforblock on iron_bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the blockstate east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the blockstate for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
When running /testforblock on iron
_bars, fences or panes the result is not as expected.As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the blockstate east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the blockstate for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
Detecting the block states of iron_bars, fences and (stained_)glass_panes does not workDetecting the block states of iron bars, fences and (stained) glass panes does not work
Detecting the directionblock states of iron bars, fences and (stained) glass panes does not work
Detecting the direction block states of iron bars, fences and (stained) glass panes does not work
Detecting the direction block states of iron bars, fences, redstone wire and (stained) glass panes does not work
Detecting the direction block states of iron bars, fences, redstone wire, tripwire and (stained) glass panes does not work
relates to
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
Affects:
- redstone_wire
- glass_pane
- stained_glass_pane
- iron_bars
- all fences
- fire
- all corner stairs (shape)
Detecting the direction block statesof iron bars, fences, redstone wire, tripwire and (stained) glass panesdoes not work
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
Affects:
- redstone_wire
- glass_pane
- stained_glass_pane
- iron_bars
- all fences
- fire
- tripwire
- all corner stairs (shape)
Detecting the direction block states for some blocks does not work
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
Affects:
- redstone_wire
- glass_pane
- stained_glass_pane
- iron_bars
- all fences
- fire
- tripwire
- all corner stairs (shape)
- cobblestone_wall
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
Affects:
- redstone_wire(directions)
- glass_pane (directions)
- stained_glass_pane (directions)
- iron_bars (directions)
- all fences (directions)
- fire (directions)
- tripwire (directions)
- all corner stairs (shape)
- cobblestone_wall (directions and up/pillar)
- grass/dirt/mycelium (snowy)
- fence_gate (in_wall)
- powered_repeater (locked)
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
Affects:
- redstone_wire(directions)
- glass_pane (directions)
- stained_glass_pane (directions)
- iron_bars (directions)
- all fences (directions)
- fire (directions)
- tripwire (directions)
- all corner stairs (shape)
- cobblestone_wall (directions and up/pillar)
- grass/dirt/mycelium (snowy)
- fence_gate (in_wall)
- powered_repeater (locked)
- flower_pot (contents)
Detecting thedirectionblock statesfor some blocksdoes not workDetecting the block states not saved in meta data does not work
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
Affects:
- redstone_wire(directions)
- glass_pane (directions)
- stained_glass_pane (directions)
- iron_bars (directions)
- all fences (directions)
- fire (directions)
- tripwire (directions)
- all
cornerstairs (shape)- cobblestone_wall (directions and up/pillar)
- grass/dirt/mycelium (snowy)
- fence_gate (in_wall)
- powered_repeater (locked)
- flower_pot (contents)
is duplicated by
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
Affects:
- redstone_wire(directions)
- glass_pane (directions)
- stained_glass_pane (directions)
- iron_bars (directions)
- all fences (directions)
- fire (directions)
- tripwire (directions)
- all stairs (shape)
- cobblestone_wall (directions and up/pillar)
- grass/dirt/mycelium (snowy)
- fence_gate (in_wall)
- powered_repeater (locked)
- flower_pot (contents)
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
Affected blocks
- redstone_wire(directions)
- glass_pane (directions)
- stained_glass_pane (directions)
- iron_bars (directions)
- all fences (directions)
- fire (directions)
- tripwire (directions)
- all stairs (shape)
- cobblestone_wall (directions and up/pillar)
- grass/dirt/mycelium (snowy)
- fence_gate (in_wall)
- powered_repeater (locked)
- flower_pot (contents)
Code analysis
For flower pots, see
MC-109353
is duplicated by
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
Affected blocks
- redstone_wire(directions)
- glass_pane (directions)
- stained_glass_pane (directions)
- iron_bars (directions)
- all fences (directions)
- fire (directions)
- tripwire (directions)
- all stairs (shape)
- cobblestone_wall (directions and up/pillar)
- grass/dirt/mycelium (snowy)
- fence_gate (in_wall)
- powered_repeater (locked)
- flower_pot (contents)
- melon/pumpkin stem (facing)
Code analysis
For flower pots, see
MC-109353
is duplicated by
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from https://bugs.mojang.com/browse/MC-109353 even though both bugs seem similar.
Affected blocks
- redstone_wire(directions)
- glass_pane (directions)
- stained_glass_pane (directions)
- iron_bars (directions)
- all fences (directions)
- fire (directions)
- tripwire (directions)
- all stairs (shape)
- cobblestone_wall (directions and up/pillar)
- grass/dirt/mycelium (snowy)
- fence_gate (in_wall)
powered_repeater (locked)- flower_pot (contents)
- melon/pumpkin stem (facing)
Code analysis
For flower pots, see
MC-109353
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from
https://bugs.mojang.com/browse/MC-109353even though both bugs seem similar.Affected blocks
- redstone_wire(directions)
- glass_pane (directions)
- stained_glass_pane (directions)
- iron_bars (directions)
- all fences (directions)
- fire (directions)
- tripwire (directions)
- all stairs (shape)
- cobblestone_wall (directions and up/pillar)
- grass/dirt/mycelium (snowy)
- fence_gate (in_wall)
- repeater (locked)
- flower_pot (contents)
- melon/pumpkin stem (facing)
Code analysis
For flower pots, see
MC-109353When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from
MC-109353even though both bugs seem similar.Affected blocks
Last updated for 1.11.2
Blockstates Properties bed[part=foot] occupied chorus_plant north, east, south, west, up, down dirt[variant=podzol], grass, mycelium snowy wooden_door[half=lower], iron_door[half=lower] hinge, powered wooden_door[half=upper], iron_door[half=upper] facing, open all fences north, east, south, west all fence gates in_wall fire north, east, south, west, upper flower_pot contents iron_bars, glass_pane, stained_glass_pane north, east, south, west powered_repeater, unpowered_repeater locked redstone_wire north, east, south, west all stairs shape pumpkin_stem, melon_stem facing tripwire north, east, south, west vine up cobblestone_wall north, east, south, west, up Code analysis
For flower pots, see
MC-109353
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=false
and
/testforblock ~1 ~ ~ minecraft:iron_bars east=true
directed at an iron_bars block with the block state east=true,north=false,west=false,south=falseWhat I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from
MC-109353even though both bugs seem similar.Affected blocks
Last updated for 1.11.2
Blockstates Properties bed[part=foot] occupied chorus_plant north, east, south, west, up, down dirt[variant=podzol], grass, mycelium snowy wooden_door[half=lower], iron_door[half=lower] hinge, powered wooden_door[half=upper], iron_door[half=upper] facing, open all fences north, east, south, west all fence gates in_wall fire north, east, south, west, upper flower_pot contents iron_bars, glass_pane, stained_glass_pane north, east, south, west powered_repeater, unpowered_repeater locked redstone_wire north, east, south, west all stairs shape pumpkin_stem, melon_stem facing tripwire north, east, south, west vine up cobblestone_wall north, east, south, west, up Code analysis
For flower pots, see
MC-109353When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=falseand
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from
MC-109353even though both bugs seem similar.Affected blocks
Last updated for 1.11.2
Blockstates Properties bed[part=foot] occupied chorus_plant north, east, south, west, up, down dirt[variant=podzol], grass, mycelium snowy wooden_door[half=lower], iron_door[half=lower] hinge, powered wooden_door[half=upper], iron_door[half=upper] facing, open all fences north, east, south, west all fence gates in_wall fire north, east, south, west, upper flower_pot contents iron_bars, glass_pane, stained_glass_pane north, east, south, west powered_repeater, unpowered_repeater locked redstone_wire north, east, south, west all stairs shape pumpkin_stem, melon_stem facing tripwire north, east, south, west vine up cobblestone_wall north, east, south, west, up Code analysis
For flower pots, see
MC-109353
When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=falseand
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from
MC-109353even though both bugs seem similar.Affected blocks
Last updated for 1.11.2
Blockstates Properties bed[part=foot] occupied chorus_plant north, east, south, west, up, down dirt[variant=podzol], grass, mycelium snowy wooden_door[half=lower], iron_door[half=lower] hinge, powered wooden_door[half=upper], iron_door[half=upper] facing, open all fences north, east, south, west all fence gates in_wall fire north, east, south, west, upper flower_pot contents iron_bars, glass_pane, stained_glass_pane north, east, south, west powered_repeater, unpowered_repeater locked redstone_wire north, east, south, west all stairs shape pumpkin_stem, melon_stem facing tripwire north, east, south, west vine up cobblestone_wall north, east, south, west, up Code analysis
For flower pots, see
MC-109353When running /testforblock on iron bars, fences or panes the result is not as expected.
As can be seen in the attachment, I ran
/testforblock ~1 ~ ~ minecraft:iron_bars east=falseand
/testforblock ~1 ~ ~ minecraft:iron_bars east=truedirected at an iron_bars block with the block state east=true,north=false,west=false,south=false
What I expected to happen was the first command to NOT find the block and the second command to do find the block.
Instead, the opposite happened. The first command resulted in the block being found, despite the block state for "east=" not matching my criteria. The second command resulted in the block not being found, giving the message:
"The block at -144, 67, -125 had the data value of minecraft:iron_bars[east=false,north=false,south=false,west=false] (expected: east=true)"Note: I was told to make an issue separate from
MC-109353even though both bugs seem similar.Affected blocks
Last updated for 1.11.2
Blockstates Properties bed[part=foot] occupied 1 chorus_plant north, east, south, west, up, down dirt[variant=podzol], grass, mycelium snowy wooden_door[half=lower], iron_door[half=lower] hinge, powered wooden_door[half=upper], iron_door[half=upper] facing, open all fences north, east, south, west all fence gates in_wall fire north, east, south, west, upper flower_pot contents iron_bars, glass_pane, stained_glass_pane north, east, south, west powered_repeater, unpowered_repeater locked redstone_wire north, east, south, west all stairs shape pumpkin_stem, melon_stem facing tripwire north, east, south, west vine up cobblestone_wall north, east, south, west, up 1 If the occupied property of the foot part is false, but the head part true
Code analysis
For flower pots, see
MC-109353
Windows 10
Java 1.8.0_51 (64 bit)
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
The Bug
In the latest snapshot, using a /setblock or /fill command to place a directional block with blockdata specifying direction, it will place the block with the block's default direction.
Steps to reproduce
| Block | Command |
|---|---|
| tripwire | /setblock ~ ~ ~ minecraft:tripwire north=true |
| redstone_wire | /setblock ~ ~ ~ minecraft:redstone_wire north=side |
| fence | /setblock ~ ~ ~ minecraft:fence north=true |
| glass_pane | /setblock ~ ~ ~ minecraft:glass_pane north=true |
| stained_glass_pane | /setblock ~ ~ ~ minecraft:stained_glass_pane north=true |
| iron_bars | /setblock ~ ~ ~ minecraft:iron_bars north=true |
Affected blocks
Note: This list might differ from the one in MC-109591.
- redstone_wire(directions)
- glass_pane (directions)
- stained_glass_pane (directions)
- iron_bars (directions)
- all fences (directions)
- fire (directions)
- tripwire (directions)
- all stairs (shape)
- cobblestone_wall (directions and up/pillar)
- grass/dirt/mycelium (snowy)
- fence_gate (in_wall)
- powered_repeater (locked)
- flower_pot (contents)
Resolving to MC-109591.
Some block states are read only and not saved server side yet, see MC-109591, that's why the stem's facing value has no effect.
Sounds like MC-109591
Works as intended per MC-109591.
Confirmed, seems like they don't save that block state to the region, as structure files also don't see difference between a fence aiming south and one making a north east corner.
Confirmed for 17w17b
Confirmed in 1.12, and also confirmed for the detect block state of an execute...detect... command. Seems like there's just no knowledge of these block states except for rendering purposes.
I'm the developer of the Nova Renderer and I've run into a variant of this issue. For the block states listed on this issue, the IBakedModel registered to the BlockShapedMapper has no BakedQuads. I'm using MCP 9.30 for Minecraft 1.10.