mojira.dev
MCPE-238027

Block transformation component not correctly applied

The minecraft:transformation component is not being applied correctly to boxes in custom blocks. If the following components aren’t defined, their behaviors (independently of one another) do not respect the given transformation values:

  • minecraft:selection_box

  • minecraft:collision_box

This bug does not have any effect on models, which always respect transformation correctly.

Demonstration

The attached screenshots demonstrate this issue. Both presented blocks have the following transformation: {"scale": [1, 0.5, 1]}; this transformation scales the block vertically by half, flattening it towards the center of the block.

The selection box of the block labeled as not having defined boxes is not being scaled. The same is not true for the block with defined boxes. While not apparent in the images, this applies independently to the blocks’ collisions, too.

Reproduction

This issue affects any custom block with the transformation component but missing either the collision or selection components. Although only scale was demonstrated, the issue also applies to translation. rotation has not been tested.

The demo screenshots and code are taken from the behavior pack in the attached world for convenience. This world can be opened (in Minecraft Preview) for inspection or unzipped to access the code associated with such.

Attachments

Comments 4

Thank you for helping us improve Minecraft! We saved your files:

[media][media][media]

Notice: the attached demo world crashes on open in Preview 26.30.21 due to MCPE-238456. The dimension definitions can be stripped from the world’s behavior pack to properly test out this issue.

Hi!
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 https://feedback.minecraft.net

Quick Links: 
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

I’d like to contest this. This is not a feature request. These 2 components are effectively present on a block whether they’re defined or not. There isn’t any indicator transformation should only be considered when explicitly defined. It forms a parity discrepancy between default values (e.g., true) and explicitly stated intents of such.

Ciosciaa

(Unassigned)

Unconfirmed

Multiple

26.20.26 Preview

Retrieved