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

Fix worldgen crash on 1.20 #2387

Merged
merged 1 commit into from
Apr 13, 2024

Conversation

Apollounknowndev
Copy link
Contributor

@Apollounknowndev Apollounknowndev commented Mar 9, 2024

Closes #2394, #2388, #2377, #2371, #2364, #2354, and #2332.

The Issue

Previously, the biome modifiers were structured so each biome tag got its own biome modifier that added a certain combination of flowers. This meant beach biomes were assigned cyan and purple flowers, badlands were assigned absalon and cyan flowers, etc.

However, issues arise when worldgen mods have biomes that fit into multiple categories. For example, a biome both tagged as a badlands biome and a mountain biome would get absalon flowers, cyan flowers, purple flowers, and cyan flowers... again? The game tries to maintain a consistent ordering of features to prevent generation inconsistencies, but when you have multiple of the same feature in a single biome the game can't really do that and it crashes as a result.

The Fix

The biome modifiers have been restructured to each biome modifier controls a specific flower type, and group biome tags were added that those biome modifiers target.

This means that instead of a modify_forest biome modifier telling the game to place the flower_purple feature in all biomes in the #is_forest tag, a purple biome modifier tells the game to place the flower_purple feature in all biomes in the #cyclic:has_flower/purple tag, which includes #is_forest, #is_beach, etc. As a result, a flower feature can never get placed twice in the same biome and no crash will occur.

@Apollounknowndev
Copy link
Contributor Author

Can fixing this be prioritized? This issue has existed for a long while now and there's still many people affected by it. This makes Cyclic flat out unusable with several big worldgen mods.

@Lothrazar
Copy link
Owner

this looks awesome thanks for your patience and hard work on this im going to check it out

@Lothrazar Lothrazar added the 1.20 label Apr 13, 2024
@Lothrazar Lothrazar merged commit 7733306 into Lothrazar:trunk/1.20 Apr 13, 2024
1 check passed
@sugan-reden
Copy link

sugan-reden commented Apr 14, 2024

Hi, thank you so much for your work. 😄

I have updated my issue #2388 , as I found that with the latest version of Cyclic, it seems to still persist.

As a fix, I have reverted back the Cyclic version and use it with Cyclic Crash Fixer. I have included more details in the update/comment.

Thanks for your hard work, I really admire what you guys do. Please keep it up! And don't forget to take care of yourselves. 😁

@kingokksa
Copy link

kingokksa commented Jun 1, 2024

提示:cyclic 1.12.9 修复了这个生成世界的问题,但在用之前请删掉Cyclic Crash Fixer,二者一起用还是会造成崩溃
Tip: Cyclic 1.12.9 has fixed this issue with generating worlds, but please remove the Cyclic Crash Fixer before using it. Using both together will still cause crashes

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

Successfully merging this pull request may close these issues.

Crash on world gen with Cyclic+Terralith
4 participants