-
Bug
-
Resolution: Unresolved
-
None
-
1.21.50.20 Preview, 1.21.40.25 Preview, 1.21.40.22 Preview, 1.21.40.21 Preview, 1.21.22 Hotfix, 1.21.23 Hotfix, 1.21.30, 1.21.40.23 Preview, 1.21.31 Hotfix, 1.21.50.28 Preview, 1.21.44 Hotfix
-
None
-
Confirmed
-
Multiple
-
1304425
Applying script-registered block custom components to a block results in that block becoming interactable, even when theĀ onPlayerInteract event listener is not active.
This makes placing blocks on the custom block a worse experience and means that many items, such as projectiles, are impossible to throw when looking at a custom block.
The original "fix" for this issue was for the block the player is holding to be placed when the custom block is interacted with, however this creates more issues than it solves, with a delay between block placements and signs being placed with no edit text screen.
Steps to reproduce:
- Import the provided example pack and apply it to a world
- Join the world and place the custom block (which can be found at the end of the Construction category in the creative menu)
- Right-click on the custom block to attempt to interact with it
Observed results:
- The player's arm swings, indicating that the block has been interacted with
- It is impossible to place several blocks in a line quickly by holding down the place button
- Some blocks, such as signs, are placed without certain functionality
Expected results:
- The block should not be interactable as the onPlayerInteract event listener is absent, meaning the player's arm will not swing
- When placing other blocks on the custom block, default block placement functionality should be used, allowing for fast building by holding down the place button
- relates to
-
MCPE-179928 Any Custom Component makes blocks interactable
- Resolved