-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
NuclearCraft Chemical Reactor crash creating Sulfur Dioxide #1168
Comments
Thanks for the report, it has been reported to the NC tracker here: tomdodd4598/NuclearCraft#507 |
Soz about it taking a while fellas - will try to get a build out soon! |
No worries, good luck with your mock-exams! |
Fixed with version 2.16f ;) |
I just saw, thanks! |
Hey turbo/niller should it be safe to drop in the update for e2e on our own or should we wait for the official update? |
Should be fine to do it manually I imagine, as nothing else about the rest of the mod has changed ;) |
If you don't use XNet gases channels, using 1.63a with updated NuclearCraft is safe. |
Cool deal thanks I'll go ahead and push this to our server, if anything comes up i'll be sure to send an issue your alls way. |
OH and is this just a server side fix or will clients also need to update? |
OK so this requires a client side update, @NillerMedDild would you mind pushing an update to 1.63a? |
I'm afraid I won't update before YNot updates. |
Roger that. I'll update my community. |
Thanks for understanding ^^ |
Absolutely! |
Modpack version
1.63a
Can the issue be reproduced?
Yes
Logs
https://pastebin.com/TU3UGHzX
Issue
A NuclearCraft Chemical Reactor fed with Molten Sulfur (from a NuclearCraft Melter of Sulfur) and Liquid Oxygen (from a Mekanism Electrolytic Separator of Water) causes a crash when it attempts to generate Sulfur Dioxide. The crash happens on the tick it would create the product - the processing ticks leading up to it are just fine.
I was able to recreate this in a brand new creative world with nothing else but those machines. This crash did not happen in 1.62.
The text was updated successfully, but these errors were encountered: