
[Bug]: Blueprint itself ruins Better End generation.
KostromDan opened this issue ยท 4 comments
We do not prioritize fixing issues present only with Sinytra Connector. Blueprint was not designed for Fabric mods, so problems are expected.
I'm also not sure what your issue is in the screenshot. You may be saying Blueprint changes the generation of chunks already loaded, which is likely not something Blueprint should have to fix.
Or, if you're saying that Blueprint changes the generation of the end, then that should be expected, as adding any biome mod is likely to have that effect.
We do not prioritize fixing issues present only with Sinytra Connector. Blueprint was not designed for Fabric mods, so problems are expected.
I'm also not sure what your issue is in the screenshot. You may be saying Blueprint changes the generation of chunks already loaded, which is likely not something Blueprint should have to fix.
Or, if you're saying that Blueprint changes the generation of the end, then that should be expected, as adding any biome mod is likely to have that effect.
Issue with generating new chunks.
Blueprint doesn't generate biomes itself, it can be used by another mods for adding biomes, so maybe that part of code which can be used for generation, changes it, despite the fact only blueprint installed.
Maybe we shouldn't apply parts of blueprint which are used for generation, if no woldgen mods using it installed.
Okay, gave it another chance. It not just changes, but ruins. for example end_midlands biome shouldn't generate at all with better_end. But it generated pretty often.
Can I change it somehow? Can you add option to prevent invading generation of some dimention?
Anyways I'll fix it, I need personality mod for my modpack, maybe I'll just threw out all classes of blueprint not requed for personality via coremodding but I don't want doing this.