Stack overflow in AbstractPNCBlockWithBoundingBlocks.onDestroyedByPlayer
Linguardium opened this issue ยท 0 comments
Describe the bug
TeamAOF/Craftoria#683
https://gnomebot.dev/paste/mclogs/SBW0pm4#L21296
https://gnomebot.dev/paste/mclogs/Rf5wiGG#L9090
Appears that onDestroyedByPlayer calls what it assumes is another block's onDestroyedByPlayer, but never actually checks that it isnt the same blockpos so its possible that it continues to call its own onDestroyedByPlayer recursively.
How to reproduce the bug
Unknown but looking at the code, i assume that you make sure BOUNDING is true and that getMainPos returns the same pos, then break it.
Expected behavior
check if the main pos returned by getMainPos is the same as the pos passed into the onDestroyedByPlayer and dont call itself again.
Additional details
player was using Craftoria modpack and reported this crash.
Which Minecraft version are you using?
1.21
Which version of PneumaticCraft: Repressurized are you using?
8.2.13