null
null
Environment
null
Comments3
History8
Changed description:
Partner Rank: 3
0Partner Team Reporting: Project Moonboot
0Verification builds: 1.13.0 1.14.30
0Summary: The variant of the block no longer shows when pressing f3 it is also not in the block debug menu.
0![]()
My understanding is that this is being replaced by block states however at this time command blocks will continue to use <block><id> below is a screenshot from 1.12 on what we should be seeing.
0![]()
Impact: This significantly increases the amount of time it takes to develop content that needs multiple command blocks checking for specific block variant <id>
00
Repro steps:
01. Open dev client and load any map. Press f3 6 times and this dialog will appear in the top left corner.
0![]()
2. Press f3 12 more times and open block debug menu
0Place a lever and look at it. The lever direction in this case a lever facing north is lever:4 which matches to lever direction.
0![]()
However when this lever is flipped. The lever_direction does not change. But doing a command like /testforblock -1 4 4 lever:4 does not return the correct <block><id>
0![]()
0
Observed Results: <block data> and more importantly the tile data <id> is not shown in any menu that I could find. While Minecraft is moving to use block states command blocks continue to use <block><id>.
00
Expected Results: Be able to see if the lever we are looking at is lever:4 or when the state is toggled lever:12. This can take time when doing large commands because the data value changes based on direction the lever is flipped and the direction the lever is facing. This also applies to other blocks such as buttons or leaves.
0Screenshots attached: Yes
0Regression Builds: 1.12.1 release
0Notes: This is also important to have for fill commands when wanting to replace one block with another but only replace blocks of a specific id. This is most used with leaves on trees as they have so many different values but only specific leaves may need to be targeted.
null
Changed environment:
Windows 10 Dev Client 1.13.0, 1.14.30
null
Changed summary:
Resolution: Unresolved → Invalid
null
Posted to wrong jura site.
Please close this request