search

ghen-git / Thirst-Mod

Other
13 stars 10 forks source link

Newest Version For 1.20.1 Not Working Properly With Appleskin #68

Closed peepeepoopoocaca closed 8 months ago

peepeepoopoocaca commented 8 months ago

I'm not sure if it's a mod conflict or something, but the newest version that's available for 1.20.1 is not showing the water saturation bar while using Appleskin.

mlus-asuka commented 8 months ago

I guess you disabled it in Appleskin config

peepeepoopoocaca commented 8 months ago

That wouldn't make sense. My config hasn't changed since updating and reverting to the previous version of Thirst Was Taken resolves the issue. Also, all of the options in my Appleskin config are set to true.

mlus-asuka commented 8 months ago

That wouldn't make sense. My config hasn't changed since updating and reverting to the previous version of Thirst Was Taken resolves the issue. Also, all of the options in my Appleskin config are set to true.

What I did in new version is just sync Appleskin config with Thirst saturation display

mlus-asuka commented 8 months ago

image

peepeepoopoocaca commented 8 months ago

I'm going to try deleting the config and reinstalling Appleskin to see if that fixes it.

peepeepoopoocaca commented 8 months ago

Still seeing this issue after deleting the old config file and reinstalling Appleskin. It could very well be a mod conflict issue, but the only mod that I could maybe see conflicting is Cold Sweat. Food saturation bar shows up fine, but thirst saturation doesn't. Very confused on this one.

mlus-asuka commented 8 months ago

wait, cold sweat on 1.20.1?

peepeepoopoocaca commented 8 months ago

Yes, Cold Sweat on 1.20.1. Also, the version of Thirst Was Taken that just came out seems to have resolved this issue. The version released on October 10th was the bugged one and it seems this issue is fixed now.

mlus-asuka commented 8 months ago

Yes, Cold Sweat on 1.20.1. Also, the version of Thirst Was Taken that just came out seems to have resolved this issue. The version released on October 10th was the bugged one and it seems this issue is fixed now.

ohh! i see. yes i did fixed it in the new version