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
When using a flamethrower in inferno mode on a block of obsidian that has another block of obsidian floating two blocks above, minecraft crashes with attached crash log. While trying to load into the affected save, minecraft crashes again, making the level unplayable.
Obisdian arrangement:
O = Obsidian
X = Air
O
X
X
O
(View from front)
Steps to reproduce:
Install Mekanism, create a new save
Build a obsidian arrangement as shown above
Equip a flamethrower, set it to inferno-mode and fire away at the obsidian
Minecraft crashes
Version (make sure you are on the latest version before reporting):
Forge: 1.16.4 35.1.36 Mekanism: 1.16.4-10.0.18.445 Other relevant version:
…6861). Also bump min forge version to 36.0.13 and add our multiblocks to the enderman place on blacklist so that endermen can't place blocks inside of them and cause them to break (#6758). Also update dependencies and datagen as needed
So it turns out this is actually caused by one of the two bugs in vanilla that caused them to release 1.16.5. As 10.0.20 will require 1.16.5 for some forge updates (as well as to have this bug fixed), I am marking it as fixed in dev even though just updating to a 1.16.5 version of forge without updating Mekanism also would fix this.
Issue description:
When using a flamethrower in inferno mode on a block of obsidian that has another block of obsidian floating two blocks above, minecraft crashes with attached crash log. While trying to load into the affected save, minecraft crashes again, making the level unplayable.
Obisdian arrangement:
O = Obsidian
X = Air
O
X
X
O
(View from front)
Steps to reproduce:
Version (make sure you are on the latest version before reporting):
Forge: 1.16.4 35.1.36
Mekanism: 1.16.4-10.0.18.445
Other relevant version:
Crash log
gist
The text was updated successfully, but these errors were encountered: