mojira.dev
MC-279530

Inconsistent naming of block states for the modes of structure blocks and test blocks

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:

  1. 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_block
  2. Enable 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

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_phase

  • trial_spawner_state

  • vault_state

  • creaking_heart_state

I assume these are intended because there is no inconsistency with a separate phase or state property.

In addition, comparators have their own separate mode block state property.

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

Despite this issue being marked invalid, the block state property for test blocks was in fact renamed from test_block_mode to mode in Minecraft snapshot 25w04a.

Avoma

(Unassigned)

Confirmed

Block states

25w03a

Retrieved