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

[1.16.5] Using versions later than 1.3.0 causes internal server lock with world start with modded biomes #54

Open
Kaleidio opened this issue Dec 13, 2022 · 4 comments
Assignees
Labels

Comments

@Kaleidio
Copy link

Kaleidio commented Dec 13, 2022

Been dealing with this issue for months now, at first I thought it was some sort of conflict, but after some investigation it seems to be an issue very particular to adding modded biomes into the mix. I have a feeling this has to do with Treasure related code, as it only breaks if you are spawning in a modded biome (BYG Rainbow Beach for example, with correct ocean biomes around it)

Yes this is a continuation of an issue that has been since deleted, however it is still relevant and this time around I have more information, even if the log still spells literally nothing for us sadly...

You can reproduce the issue by installing BYG, Gottschcore. Additionally you can install Ksyxis to tell if the world is about to lock your server up by watching generation go past 0% for no reason (usually an indication of a structure generator forcing itself when it shouldn't. Ksyxis should always cause that screen to stay at 0% before spawning the player into the world). note that the freeze is rare.

@Kaleidio Kaleidio changed the title [1.16.5 [1.16.5] Using versions later than 1.3.0 causes softlock on startup with modded biomes Dec 13, 2022
@Kaleidio Kaleidio changed the title [1.16.5] Using versions later than 1.3.0 causes softlock on startup with modded biomes [1.16.5] Using versions later than 1.3.0 causes internal server lock with world start with modded biomes Dec 13, 2022
@gottsch gottsch self-assigned this Dec 13, 2022
@gottsch gottsch added the bug label Dec 13, 2022
@gottsch
Copy link
Owner

gottsch commented Feb 6, 2023

Do you still have this issue with the latest version of Treasure (v2.3) - it came out on the 1/3 ?

@Kaleidio
Copy link
Author

Kaleidio commented Feb 6, 2023

I don't have treasure installed, I think it's library code meant to tie in treasure at fault. and yes the issue still exists.

@Kaleidio
Copy link
Author

Kaleidio commented Feb 6, 2023

@Kaleidio
Copy link
Author

Kaleidio commented Feb 6, 2023

I see a lot of references in this code that sort of rebuild everything forge already provides in its API. this isn't safe for mods as some mods may be providing completely custom tags and biome noise/accessor classes (especially BYG). Most of these classes, which also seem to be singletons, should be replaced with actual Forge references instead, to make sure everything registered is as dynamic as can be.

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

No branches or pull requests

2 participants