-
Notifications
You must be signed in to change notification settings - Fork 79
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
IE's Pipe plus QS' Fluid Trash Can = CME upon world load #4858
Comments
oh god it's so much worse, it's not related to the Tank or redstone at all! |
@sam-kirby possible and/or worth fixing in SevPatches? |
I haven't had a chance to look into this at all yet, but the last release of SevPatches (which hasn't made it into SevTech yet) fixed a CME during chunk loading - you could give it a try and see if this is actually that same issue in a different hat? https://www.curseforge.com/minecraft/mc-mods/sevpatches/files/5142938 |
Good news, using that SevPatches 1.12.0-15 release instead of the 1.9-10 I was using, my formerly bricked test worlds loaded without issues, so it does seem like it's the same fixed issue, kudos! |
Bug Description
This simple 3 block setup, using Immersive Engineering and Quantum Storage, causes the world to become unloadable. A crash will occur every time upon loading it.
Metal Barrel (IE) > Fluid Pipe (IE) > Fluid Trash Can (QS)
Note: The in-game restore backup feature errors out and It seems to corrupt the JourneyMap data as well, I had to both manually restore a backup and delete the world's JourneyMap data to fix my world.
I'm not 100% sure if it's either a DarkPacks or IE bug, but an unloadable world is a really catastrophical bug, so I figured I'd report it.
Addendum: while this bug occurs with Quantum Storage's Fluid Trash Can, it turns out that Cyclic's Trash Void works A-OK, go figure.
Did this behavior use to work in the previous version?
N/A
Steps to Reproduce (for bugs)
No need to fill the Barrel, it'll crash just the same if it's Empty
Logs
Client Information
World Information
The text was updated successfully, but these errors were encountered: