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

Crashing on world load after updating to latest dev snapshot #12

Closed
klaidas01 opened this issue Jun 9, 2024 · 3 comments
Closed

Crashing on world load after updating to latest dev snapshot #12

klaidas01 opened this issue Jun 9, 2024 · 3 comments

Comments

@klaidas01
Copy link

Pack Version:
dev-579c535

Description:
After updating from 1.3-rc-20230128 to the latest dev snapshot (using curse forge launcher) minecraft crashes on world load. Looks like the crash is caused by electric blast furnaces which were running at the time of saving the world, idle blast furnaces load without issue

Expected Behavior:
World should load without crashing

Steps To Reproduce:
Create a world in 1.3-rc-20230128 and save with blast furnaces running. Move save to dev-579c535 and try loading the world.

Crash Log:
crash-2024-06-09_11.51.28-server.txt

@Exaxxion Exaxxion transferred this issue from Nomifactory/Nomifactory Jun 9, 2024
@Exaxxion
Copy link
Collaborator

Exaxxion commented Jun 9, 2024

Transferred to GTNE repository. I see the issue in the code. Thank you for reporting the issue.

@Exaxxion
Copy link
Collaborator

Exaxxion commented Jun 9, 2024

@klaidas01 Please try replacing the 1.18.2 jar with the 1.18.3 jar in your mods folder. If you want it before it's processed and approved on CurseForge, you can get it from the GitHub releases page.

When updating from an older version, the active smelt won't enforce coil-specific jamming constraints as a fallback, as it won't have any recorded. It will enforce them normally for all recipes after that one completes. Most importantly, it will not crash.

@klaidas01
Copy link
Author

klaidas01 commented Jun 9, 2024

Everything seems to be working with 1.18.3, thanks for the quick fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants