Cold Sweat

Cold Sweat

3M Downloads

[1.20.1] Error Parsing Biome Temp Config - Inhospitable Biomes

MysticcFibrosis opened this issue ยท 5 comments

commented

Upon loading up my game, I get the following errors in my log for all biomes:

image

This seems to result in all biomes not having the proper temperature settings (and also gives me the Inhospitable advancement on world load). I thought it might be an issue with my other mods, but it occurs even with just Cold Sweat and Biomes O' Plenty.

I'm using Cold Sweat 2.2.5.1 on Forge 47.2.0.

commented

This occurs normally, even when things aren't wrong. This is because the configs are loaded twice, once when the game first boots, then again when the world is loaded. Because biomes aren't loaded when the game is first started, they appear as "nonexistent" in the eyes of Cold Sweat. This is why the error log says "the biome may not be loaded yet", because in this case it isn't.

In any case, I can't re-create your strange behavior in the same setup. I will say that your forge version is pretty out-of-date, though. It's 20 versions behind. This may be it, I have no idea because I don't have the full log

commented

I can share my latest.log:

latest.log

As for the Forge version, yeah. I used the version that Prism Launcher defaulted my custom instance to, but after updating to 47.2.20 the same strange behavior seems to occur. It could possibly be a Prism Launcher instance thing, but I wouldn't know what to do about that other than recreating my instance.

commented

For whatever reason, the biome temperatures seem fine now? I didn't change anything, just re-added the Cold Sweat JAR to my pack. I don't know why, but I think that might have been a separate issue from getting the Inhospitable advancement on world load, since I'm still encountering that.

commented

Updating this to say that I tried recreating a new instance in Prism Launcher with just Cold Sweat, Biomes O' Plenty, and Terrablender on Forge 47.2.20, and the same issue occurred. All biome temperatures seem to be set incorrectly, and no matter where I spawn it is Inhospitable.

commented

Very interesting indeed. I couldn't tell you one way or the other. I'm glad you were able to resolve it regardless.