BlockEvent.PLACE has the wrong BlockState parameter on Fabric.

Question

Lemonszz opened this issue 2 years ago · 1 comments

Lemonszz commented 2 years ago

On a Fabric client, the state passed into BlockEvent.PLACE is the block that is currently in the position instead of the block that will be placed.

Forge is unaffected.

Tested with Architectury API 8.1.79 for MC 1.19.4

I didn't look into it too much, but I believe it was caused by this bug fix..

MaxNeedsSnacks · Answer 1 · 2023-05-04T07:25:00.000Z

Urgh, good catch... That should probably mirror Vanilla and call getPlacementState(context) instead