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.

Sign up for GitHub

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

Jump to bottom

Crash if "Oceanic Expanse Compatibility" is True at 0.2.18 #352

Open
magianiam opened this issue Mar 5, 2024 · 4 comments
Open

Crash if "Oceanic Expanse Compatibility" is True at 0.2.18 #352

magianiam opened this issue Mar 5, 2024 · 4 comments
Labels
bug Something isn't working compatibility Compatibility issues with another mod upcoming fix Author has fixed the issue, but has not released an update to close the issue

Comments

@magianiam
Copy link

Use version Future-MC-0.2.18.jar

Crashes after world creation
crash-2024-03-05_12.36.48-server.txt

"Oceanic Expanse Compatibility" to Flase solved the problem.
@thedarkcolour
Copy link
Owner

That isn't an error with Future MC. Try setting it to true again and if it still crashes, send that log?

@magianiam
Copy link
Author

I set the setting to true
Crash occurred immediately after world creation

crash-2024-03-05_17.02.49-server.txt
latest.log

@thedarkcolour
Copy link
Owner

Try removing Fermium

@thedarkcolour
Copy link
Owner

Nevermind, this is a Future MC issue. In the meantime, you can fix this by removing all of the default biomes from the fish configs in Future MC.

@thedarkcolour thedarkcolour added bug Something isn't working upcoming fix Author has fixed the issue, but has not released an update to close the issue compatibility Compatibility issues with another mod labels Mar 5, 2024
@Sereath Sereath mentioned this issue Mar 8, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working compatibility Compatibility issues with another mod upcoming fix Author has fixed the issue, but has not released an update to close the issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thedarkcolour @magianiam