-
Notifications
You must be signed in to change notification settings - Fork 13
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
Crash with preset Curios API configuration #287
Comments
So I did that. Now the world technically doesn't crash, just freezes upon world loading screen. No crash report generated, but I found this in the log: Encountered an unexpected exception Any idea where the problem resides? |
Sorry, I didn't see this till now. My bad. |
Are you still getting this? Can you post your curios-server.toml or maybe it is your tags? |
Not getting this crash now, but another one @ #300 |
This issue has been fixed after messaging the mod owner and sorting it out with them. However for some modpacks, if this mod is added ensure that all Curios slots are enabled. If any are disabled it will give a Ticking Player crash with the details 'Java.lang.RuntimeException: Slot 0 not in valid range - [0,0).
You can edit the config files of Curios in the saves of your worlds to ensure none are set to 'Size=0' which disables them.
crash-2022-04-12_14.36.54-server.txt
The text was updated successfully, but these errors were encountered: