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

NuclearCraft Chemical Reactor crash creating Sulfur Dioxide #1168

Closed
MirrorImageQS opened this issue May 2, 2019 · 15 comments
Closed

NuclearCraft Chemical Reactor crash creating Sulfur Dioxide #1168

MirrorImageQS opened this issue May 2, 2019 · 15 comments
Labels
Mod Issue Status: Blocked This issue cannot be closed until another open issue or PR is closed

Comments

@MirrorImageQS
Copy link

MirrorImageQS commented May 2, 2019

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.

@NielsPilgaard
Copy link
Collaborator

Thanks for the report, it has been reported to the NC tracker here: tomdodd4598/NuclearCraft#507

@NielsPilgaard NielsPilgaard added Status: Blocked This issue cannot be closed until another open issue or PR is closed Mod Issue labels May 3, 2019
@tomdodd4598
Copy link

Soz about it taking a while fellas - will try to get a build out soon!

@NielsPilgaard
Copy link
Collaborator

No worries, good luck with your mock-exams!

@tomdodd4598
Copy link

Fixed with version 2.16f ;)

@NielsPilgaard
Copy link
Collaborator

I just saw, thanks!

@arcreigh
Copy link

arcreigh commented May 5, 2019

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?

@tomdodd4598
Copy link

Should be fine to do it manually I imagine, as nothing else about the rest of the mod has changed ;)

@NielsPilgaard
Copy link
Collaborator

NielsPilgaard commented May 5, 2019

If you don't use XNet gases channels, using 1.63a with updated NuclearCraft is safe.

@arcreigh
Copy link

arcreigh commented May 5, 2019

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.

@arcreigh
Copy link

arcreigh commented May 5, 2019

OH and is this just a server side fix or will clients also need to update?
@turbodiesel4598

@arcreigh
Copy link

arcreigh commented May 5, 2019

OK so this requires a client side update, @NillerMedDild would you mind pushing an update to 1.63a?

@NielsPilgaard
Copy link
Collaborator

I'm afraid I won't update before YNot updates.

@arcreigh
Copy link

arcreigh commented May 5, 2019

Roger that. I'll update my community.

@NielsPilgaard
Copy link
Collaborator

Thanks for understanding ^^

@arcreigh
Copy link

arcreigh commented May 5, 2019

Absolutely!
Thanks for the great pack!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mod Issue Status: Blocked This issue cannot be closed until another open issue or PR is closed
Projects
None yet
Development

No branches or pull requests

4 participants