You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When placing a conduit type block (including heat cables, fluid tubes, and alchemy conduits), if the conduit would have a connection immediately upon placement, the placement does not cause a block update, regardless of flags on the original setBlockState call.
Additional context [Optional]
This is a low impact edge case.
Describe the bug
When placing a conduit type block (including heat cables, fluid tubes, and alchemy conduits), if the conduit would have a connection immediately upon placement, the placement does not cause a block update, regardless of flags on the original setBlockState call.
Additional context [Optional]
This is a low impact edge case.
This is caused by this call: https://github.com/Da-Technomancer/Crossroads/blob/1.16/src/main/java/com/Da_Technomancer/crossroads/API/templates/ConduitBlock.java#L170
Which is called during World::setBlockState
This call results in this call: https://github.com/Da-Technomancer/Crossroads/blob/1.16/src/main/java/com/Da_Technomancer/crossroads/API/templates/ConduitBlock.java#L306
Turns out calling World::setBlockState at a position during another World::setBlockState call at that position overwrites the previous flags, causing the flag parameter to be 2 regardless of the initial value.
Block updates require (flag & 1) != 0 to occur.
The text was updated successfully, but these errors were encountered: