V2.1 EXP

What's annoying is that Redbeardt fixed the armor dye issue with his Dyeable mod, allowing you to dye armors again. It worked until v2.0 broke it.

So basically TFP broke armor dyes with v1, and then broke Redbeardt's fix with v2, and with v2.1 have made things even worse by making it even more difficult (if not impossible) for a modder to fix.

Like... WHY. 🤦‍♂️

If a modder wants to re-add the tags, nothing is stopping them from doing that.
 
Thank you for your continued hard work! <3 While the change and fix lists are (relatively) small, I do appreciate most of them! hehe I am a little disappointed there appears to be the final nail in the coffin for dyeable armours, but it is what it is. Hopefully the road to experimental release runs smoothly (assuming you mean by next Saturday)!
 
I misunderstood the post, then. That's good to hear.

Of course, I have no idea why or how v2 broke the Dyable mod, so for all I know it may no longer be fixable via mod.

From what I've heard, the cosmetic slot would remain nonfunctional however, which could provide a bit of a headache to modders. :/
 
What do you mean by "Log serverconfig settings not compatible with consoles when ServerAllowCrossplay is set to true?" You've added Incompatibility?

"Clients hit by projectiles now play specters grace audio" - What is "Specters grace audio"?
 
What do you mean by "Log serverconfig settings not compatible with consoles when ServerAllowCrossplay is set to true?" You've added Incompatibility?

"Clients hit by projectiles now play specters grace audio" - What is "Specters grace audio"?
1. There was incompatibility. That's something they fixed.
2. That's the name of the sound they used. Once you hear it, you can say: "Hey! I know how it's called." 😁
 
Last edited:
From what I've heard, the cosmetic slot would remain nonfunctional however, which could provide a bit of a headache to modders. :/

Ugh, okay. Yeah, I just didn't think it through. I haven't really paid any attention at all to the new v2.0 cosmetic system and so I didn't consider the massive amount of changes to all that code. Of course Redbeardt's mod wasn't going to be compatible with it, lol.

Maybe it's possible to rework the dyes so that they are consumables instead of being slotted items...
 
What do you mean by "Log serverconfig settings not compatible with consoles when ServerAllowCrossplay is set to true?" You've added Incompatibility?

"Clients hit by projectiles now play specters grace audio" - What is "Specters grace audio"?

"Log" is the verb in this. So if someone has a server that allows crossplay the log will tell him which settings would prevent that
 
You mean like a 24h- 24h cycle? 🤣
I actually have yet to try out the 2.0 version properly.
You're going to be sorely disappointed. You can't exceed about 5h 30m real time, due to how timescaling doesn't take decimals into consideration, once the number dips below 1, say .95, it'll round down to 0, making time never move forward.
Fun fact: 60 minute days is actually 68 minutes, and 120 minute days it actually ~136.
 
I misunderstood the post, then. That's good to hear.

Of course, I have no idea why or how v2 broke the Dyable mod, so for all I know it may no longer be fixable via mod.
The tags are just an XML tag. They can be added back if desired. But the consequence of them being there (without a mod that deals with that) is that it creates the possibility of getting error messages in console if you try to equip the dye and can allow duping mods in the armor. If that mod prevents those issues since it allows dying armor, then the mod should be fine if it just adds those tags back. I'm sure the mod author will know how to to do that.
Post automatically merged:

Waiting for this to be fixed. Its literally a game breaking cheat. Not sure why stuff was put ahead of this
Possible reasons include:
  • Took too long to get fixed and they needed other fixes released sooner.
  • Lower priority for the devs.
  • More difficult to fix than other things that might be easier to quickly fix.
In any case, it's only game breaking if people use it. And then, it's only game breaking if the people using it consider it game breaking (some people like using cheats and exploits). Really, the only point where it becomes an issue is on a server with random people. That doesn't make it less of an issue, and it certainly needs fixed, but the scope of the problem is relatively low compared to a bug that affects all players.
 
Noticed this was some what mentioned page back.
Just a thought and more immersive, instead of having a Storm Warning noise and text on the screen (like now) how about having it displayed to the player as a realistic sky dome and weather effects with sound - like you do for the Blood Moon would be so much better possibly maybe ?
 
Back
Top