BetterEnd (Forge)

BetterEnd (Forge)

11M Downloads

BetterEnd (Forge) biomes not generating when combined with Biomes You'll Go (BYG)

Sylvannes opened this issue ยท 7 comments

commented

Hello,

Last night we've been testing mod configurations and it turns out BetterEnd biomes were not generating in the End when Biomes You'll Go was also loaded. BYG biomes did generate but BetterEnd entirely did not.

I've verified this with /locatebiome commands as well as just flying around for 10-15 minutes.

I've then tested a Fabric loader world with both Fabric versions of these mods, and the biomes did generate properly without a problem.

So this seems to be a problem specific to the Forge version(s) and interactions of these mods.

Thank you for all your work on these amazing mods.

Small update for info:

  • This is on MC1.16.4 with latest Forge.
  • This also seems to happen with older versions of Forge.
  • The mod description does state BetterEnd and BYG should be compatible so hopefully it's nothing too complicated.
commented

I am not sure why you are experiencing that, i just tested a new world with BYG and BetterEnd installed and everything was working perfectly, as in earlier versions of the mod. you said you were testing configurations, what did you change?

commented

Thanks for the reply. I have not changed anything in custom configuration of Minecraft or mids themselves. This is just running a list of mods.

I just tested a new world with only these mods to verify that the problem is not somehow in another part of the mod list:

betterendforge-1.16.4-1.4.1
byg-1.1.8
chocolate-1.2.0-1.1.6.4 (dependency for BYG).

This setup still only seems to spawn BYG biomes and not BetterEnd biomes.

Small screenshot of /locatebiome command tests in the End:
image

I've also just tested renaming the byg jar to a_byg-1.1.8 to try and see if the load order matters in this case but the same thing happens.

Not entirely sure what's going on. Next step for me would be to look at the configuration and see how the biome seeding is set up after creating a new world maybe?

commented

Strange. My test was definitely with default world settings.

But I did just test adding in another generation mode (Biomes O' Plenty) and now both BYG and BetterEnd are generating in the End. I have no idea why but adding BOP into the mix just magically fixes the problem its seems. Must be some sort of configuration/bootstrapping conflict issue maybe.

Note: So this is when you set world type to Biomes o' Plenty, it somehow also seems to fix the original bug and now all three generator mods work.

commented

Small update: If I run BetterEnd alone, the biomes generate correctly. Looking at the WorldGenSettings of level.dat with NBTExplorer it shows this setting:

image

But when I run with both BYG and BetterEnd, the setting looks like this:

image

I'm not sure whether this is actually a problem or is any indication, just noticed it after checking based on this article: https://github.com/paulevsGitch/BetterEnd/wiki/Tutorials#how-to-fix-wrong-biome-source

commented

For me it's working, it's the only two generation mods I have alongside quark stuff and other dungeon things and it is working perfectly fine, didn't have to fiddle around or anything. I have noticed, however, that a lot of generation mods fail to work if you are in an amplified world (not saying this is your case unless it is)

commented

Not sure what was happening there, but i tested myself with the same Forge version and same mods versions as you and i can confirm that BYG integrates perfectly with BetterEnd as always..also the fact that the end biome source was set to BYG's is not really that important, as BYG will still gather all available biomes and include them in its generation. Of course, if you wanted to use BetterEnd custom end generator you would have to change the end biome source. On top of that, its also pretty strange that the byg end biome source was set by default, as whenever i run the two mods together BetterEnd's biome provider always took priority

commented

Closing this for now. Please, report if the issue happens again.