Crash when placing machines with stored energy
Anthony-LXXV opened this issue · 11 comments
Please use the search functionality before reporting an issue. Also take a look at the closed issues!
Issue description:
Crash when placing machines with stored energy
Steps to reproduce:
- Place machine.
- Charge it.
- Remove it.
- Crashes when machine is placed back.
####Version (make sure you are on the latest version before reporting):
Forge:31.1.1
Mekanism-1.15.2-9.9.9.401
Other relevant version:
Crashlog
https://pastebin.com/JKSuwdJV
I don't think that mekanism is the issue but i would need lastest.log to confirm that.
latest log
https://pastebin.com/msm96pS4
From the crash log this looks like an issue with inventory generators, my guess is that they are caching or doing something odd that makes it so that they think you still have the item in your inventory after you have placed it. Given there should be no way that our capability is on the empty stack, but given inventory generators has not updated their source on github past 1.12, there is not much more I can do on my end to see if it is a bug on our end, or just an issue with something they are doing.
I was using the beta from from curseforge,
inventorygenerators-1.15.1-1.0.1.jar
Same crash happened with the player transmitter in my (Powah!) mod.
Minecraft: 1.15.2
Forge: 31.1.14
Mekanism: 1.15.2-9.9.10.402
Crash log: https://pastebin.com/ksHhyjN4
Asking some questions in the forge discord to see where this needs to be fixed (if I need to add a check for it being air, or if I need to make a PR to forge), but from what I can tell it has to do with the fact that item stacks don't invalidate their attached capabilities when they become empty.
Still not fully sure it is not partially a forge problem but added a patch/fix that will at least stop the crash from our side for the next alpha.
That's so weird because the crash happen even when i'm in creative mode, i mean when the item stack doesn't shrink or set to air, sorry for late answer.
Closing as 9.9.11 is now released and on curseforge, and from my testing this issue no longer occurs.