Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash when using a flamethrower in Inferno-Mode on obsidian #6861

Closed
kienhoefr opened this issue Jan 10, 2021 · 1 comment
Closed

Crash when using a flamethrower in Inferno-Mode on obsidian #6861

kienhoefr opened this issue Jan 10, 2021 · 1 comment
Labels
1.16 bug Fixed in dev Not Mekanism issues caused by another mod
Milestone

Comments

@kienhoefr
Copy link

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:

  1. Install Mekanism, create a new save
  2. Build a obsidian arrangement as shown above
  3. Equip a flamethrower, set it to inferno-mode and fire away at the obsidian
  4. 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:

Crash log

gist

@pupnewfster pupnewfster added 1.16 To be confirmed Looks like a bug, hasn't been confirmed by a dev labels Jan 10, 2021
@pupnewfster pupnewfster added this to the 10.0.19 milestone Jan 10, 2021
@pupnewfster pupnewfster added bug Not Mekanism issues caused by another mod and removed To be confirmed Looks like a bug, hasn't been confirmed by a dev labels Jan 30, 2021
pupnewfster added a commit that referenced this issue Jan 30, 2021
…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
@pupnewfster
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.16 bug Fixed in dev Not Mekanism issues caused by another mod
Projects
None yet
Development

No branches or pull requests

2 participants