mojira.dev
MCPE-238017

Client-side placement is incorrectly enabled for blocks that apply custom components using the "permutations" array

When a block that is being placed has a custom component with the beforeOnPlayerPlace hook, it should not be placed on the client-side until this hook has ran on the server to avoid the placed permutation differing between the client and server.

However, when the custom component is applied in the permutations array, the game does not correctly identify that client placement should be prevented.

Steps to reproduce:

  • Download the attached add-on which adds a custom head block.

  • Place the block on top of other blocks.

Observed results:

  • The head does not initially face towards the player, taking a moment to update its direction

Expected results:

  • The beforeOnPlayerPlace hook should run before the block appears to the client, preventing the direction of the head from shifting.

  • Client placement should still be supported when the head is being placed on the side of another block, as the custom component is only applied when the minecraft:block_face state is "up".

Attachments

Comments 3

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

[media][media]

This issue has been reviewed by our team.

Please add new, relevant information if it helps us understand or reproduce the issue. To show that you’re affected, use the vote feature rather than commenting.

If a fix is implemented, it will be listed in our official changelogs.

For major outages or urgent assistance, visit the Minecraft Help Center.

It appears the issue affects beforeOnPlayerPlace as a whole, waiting a tick before performing an action. Ex. this results in ghost blocks being placed when using event.cancel.

QuazChick

(Unassigned)

1611024

Confirmed

Multiple

26.20.26 Preview, 26.30.27 Preview, 26.20

26.30.29 Preview, 26.30

Retrieved