Cold Sweat

Cold Sweat

5M Downloads

"dimensions" in Temperature Regions config only applies to #forge:overworld_like Tag

ThisOneMadow opened this issue · 9 comments

commented

WB, as said above, from what I noticed while making the temp_region file, giving it a specific dimension or tag doesn’t seem to work at all. The config always only applies to the Overworld or any overworld-like dimensions.

I tested this with multiple dimensions such as blue_skies:everdawn, aether:the_aether, deeperanddarker:otherside, and even the Nether itself. The only dimensions that were affected are from Blue Skies, Overworld, and Aether.

I’ve also tried multiple tags, but it always comes down to only working with overworld-like dimensions.

commented

Can you send what you tried, just to be sure? I know for sure that making temperature regions for the Aether works; I tested it not long ago.

commented

Sure, heres the config: https://gist.github.com/ThisOneMadow/4817571054ba930d11dc0df5bd8040bc
(It’s a bit messy, I’ve been testing some things lol.)

Yes, the config works like it should, except that it’s also being applied to the Overworld. Even though I set it up so it should only be applied to the Aether. So I think it might be some kind of bug with the "dimensions" field. (being applied always to the tag I mentioned.)

commented

Creating a simple temp region in a datapack worked in the Aether and did not affect the Overworld or any other dimensions. I did notice that your temp region file has some overlapping regions, which might lead to unexpected behavior. Maybe it's that?

commented

I’m pretty sure that’s not might be the issue. I’ve been working with two configs to try and fix it: the one I already sent you, and another one here: https://gist.github.com/ThisOneMadow/5162f70ebb800bbb659aefbbb5ad11dc
That second one should only disable cave insulation (found it on Discord), but no surprises, still being applied to the Overworld too.

Today I was thinking maybe it’s the version or some Aether addons messing with it, but here’s what I tried:
-Using the configs in my modpack (Forge 1.20.1)
-New instance with only Aether & Cold Sweat (with and without Aether addons), still Forge 1.20.1
-Testing on the newest possible version with Aether and Cold Sweat (NeoForge 1.21.1)

Every time I switched between the 2 configs but the dimensions field being still very stubborn.

For clarity, I’ve been using the data folder method in the Cold Sweat config. Haven’t tried the traditional datapack way, but I’d expect it to act the same lmao.

Not really sureee what else I could try at this point.

commented

Maybe try applying it as a datapack just to be sure. Configs and datapacks are loaded through different ways, so there is the possibility. I assumed you were using a datapack, so that's how I've been testing it

commented

When you said that, I actually thought maybe it could work, so I made a datapack in a new world folder and removed the one in the cold sweat config. But it gave me the exact same result.

I honestly don’t get how you got this to work when I feel like I’ve been doing the exact same things and it should work. I’ve been trying to get this working for about 2 weeks now (not even counting when I tried it months ago cough cough) I would ask for the config file you used, but I feel like it wouldn't be much difference.

commented

I'm testing your config again, and I really do think it's the overlapping temperature regions causing issues. Also, using "ground_level" in the Aether is problematic since there isn't a consistent ground; the system will definitely behave in unpredictable ways.

Using your config, there is essentially no temperature change between y=0 and the build limit; then when I addressed these two things, the temperature region behaved exactly as expected. Just so we're on the same page as well, I'm using CS 2.4-b05a on 1.21

commented

.......ACTUALLY, it looks like updating to the newest BETA (2.4-b05a) did the trick. Before, I was on the newest RELEASE which is 2.3.13, since I just clicked Install without selecting a version... sigh.

Now my config is messed up like before, but at least it’s only affecting the Aether and not the Overworld. Which is exactly what I wanted.

So.. yeah, it was a mod's version issue. And the config files are much more cleaner on beta version.. geez, thanks so much for helping! I’ll tweak the config based on what you said, but the important thing is the config finally only applies to the Aether and nowhere else. Tysm and keep the great work! :D

commented

I'm glad we could get this all figured out. Sorry for the confusion. The documentation is geared toward the latest beta, so it could be that the different formatting was causing the config to apply incorrectly. Thanks for your patience :)