Update chain is triggered when BlockPlaceEvent is cancelled

[Tamikaschu]

Expected behavior

The Block Update Chain should not be triggered by other blocks placed when BlockPlaceEvent is cancelled.

Observed/Actual behavior

The Block Update Chain is triggered by a block placed even though the BlockPlaceEvent is cancelled. This leads to some blocks breaking when set with worldedit or triggering redstone signals (e.g in protected areas with worldguard)

Belows case: The redstone torch can trigger the update chain of minecraft. It is an indirect block update and triggers the redstone comparator.

Steps/models to reproduce

• build a machine like shown in the gif.
• cancel BlockPlaceEvent (or protect the area with worldguard)
• set a redstone torch
• (watch the blocks updating)

Plugin and Datapack List

FastAsyncWorldEdit, floodgate, PlotSquared

Paper version

This server is running Paper version git-Paper-264 (MC: 1.20.2) (Implementing API version 1.20.2-R0.1-SNAPSHOT) (Git: 230682d) You are 54 version(s) behind Download the new version at: https://papermc.io/downloads/paper

Other

It may be worth taking a look into https://github.com/IntellectualSites/PlotSquared/issues/4210

[lynxplay]

Accepted, caused by the onRemove logic on the RedstoneTorchBlock being called when the original state is updated.

[ch4ika]

is there any news about this? will it be fixed?

[DevinGebauer]

same problem on my network