Persistent .xml changes

[RySwooperTrooper]

So...I make edits to a few xml files for the private server I run with my friends. Problem is, everytime the game updates, all the xmls are reset to defaults. I've tried making backups of the xmls I changed, but I can't just replace the new files whenever an update happens, as there is new info in the new xmls that aren't in the old xmls. Is there some special way to preserve these settings so they persist across updates, or am I just doomed to have to hunt, peck, and change xml values every single time there's an update? Thanks.

[DthBlayde]

If you're trying to play long term on the unstable, experimental, then yes. The special way of avoiding that is to way for it to go stable. You'll at least be afforded some time between updates. Experimental could be updated daily if TFP were so inclined, so you'd be stuck updating and changing each time.

[RySwooperTrooper]

Originally posted by DthBlayde:

If you're trying to play long term on the unstable, experimental, then yes. The special way of avoiding that is to way for it to go stable. You'll at least be afforded some time between updates. Experimental could be updated daily if TFP were so inclined, so you'd be stuck updating and changing each time.

Yeah, unfortunately, we all wanted to play on the experimental branch to check out the new 1.0 updates. We also hoped that would mean that when the official release happened, we wouldn't have to scrap our saved world.

[CatPerson]

If a game update doesn't specifically alter anything re: the changes/edits you're making, a modlet might help - versus direct edits to the .xml's themselves I mean. You'd have to learn how to make modlets. There's probably guides around I assume.

Updates will overwrite those .xml's, as you've discovered, so you have to keep constantly re-editing them manually. I think the notion behind the modlet is they override what's in the default .xml's - again, assuming that specific element or paths hasn't been changed. Which is why some (simpler/basic) modlets work after an update, and some won't etc.

[JimmyIowa]

Tou need to use modlets, which are xpath line edits to the original file, instead of changing the original game files in the \config folder.

Updates, and game verifies will always return the original files to their proper original state. And they should. Because that is actually their function.

Modlets, which are placed in the \Mods folder, persist between updates. (However, if the update changes the exact line that your modlet changes you might have a conflict which makes you modlet outdated.)

[Capt. W. Schwartz]

As JimmyIowa said, a modlet is what you need to write.

https://community.7daystodie.com/topic/7653-xpath-modding-explanation-thread/
https://7daystodie.fandom.com/wiki/XPath_Explained
https://community.7daystodie.com/topic/35840-v2-of-modinfoxml-template-for-game-v1x/

What kind of edits are we talking about? Some of us might have a modlet that does what you need, or be able to point you in the right direction.

[RySwooperTrooper]

Originally posted by Capt. Q. Schwartz:

As JimmyIowa said, a modlet is what you need to write.

https://community.7daystodie.com/topic/7653-xpath-modding-explanation-thread/
https://7daystodie.fandom.com/wiki/XPath_Explained
https://community.7daystodie.com/topic/35840-v2-of-modinfoxml-template-for-game-v1x/

What kind of edits are we talking about? Some of us might have a modlet that does what you need, or be able to point you in the right direction.

They're very simple things. Edits to the progression.xml to modify exp level scaling, changes to trader.xml to make the traders open 24/7. Yeah, i think modlets would be the way to go. As Jimmy said, I get the importance of being able to return the original xmls through updates/verification, I just needed a way to retain the changes I made since I can't flat out swap the xml files after an update. I'll look into these. thanks!