The Bug:
Inconsistent naming of block states for the modes of structure blocks and test blocks.
Structure blocks refer to their mode state as "mode" while test blocks refer to their mode state as "test_block_mode". This is inconsistent.
Steps to Reproduce:
Summon both a structure block and a test block using the command provided below.
/setblock ~1 ~ ~1 minecraft:structure_block/setblock ~1 ~ ~1 minecraft:test_blockEnable the F3 debug screen and look at the block states of both of the blocks.
Observed Behavior:
There is inconsistent naming of block states for the modes of structure blocks and test blocks.
Expected Behavior:
The naming of block states for the modes of structure block and test blocks would be consistent.
Linked issues
Comments 3
Thank you for your report!
After consideration, the issue is being closed as Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit The official Minecraft feedback site or visit the Minecraft Feedback Discord server.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
There seems to be a change in name convention for block state properties, with more properties getting their relevant block prefixed in their name. For example:
sculk_sensor_phasetrial_spawner_statevault_statecreaking_heart_stateI assume these are intended because there is no inconsistency with a separate
phaseorstateproperty.In addition, comparators have their own separate
modeblock state property.