Subscribe to download
Artificed Patches - EBF

That all makes perfect sense. :D Rimworld and its xml/code is an enigma lmao We have hundreds of ongoing memes about it all. But yeah, I'm honestly surprised it ever worked properly for you at the start. lol And I totally get the apprehension about joining a new public forum of any kind. The Rimworld server is like 60k users large but that's a good thing. The mod-dev channel has an insane amount of knowledge, way way waaaay more than what we could ever hope to put up on any wiki. Plus you'd get real-time feedback and help. Whatever you do though, enjoy the modding adventures!!

I do appreciate you taking the time to explain this all. I think most of my hostility and stubbornness comes from the fact that I tested my patches extensively back when I first published them and never ran into these issues, so it's very frustrating to learn that somehow it stopped working, or perhaps was never working for anyone else this entire time and I had no idea.

As for the Discord thing... I've been on both ends of this, both joining servers to ask questions and being an established server member having to answer the same FAQs day after day, and I suppose it's just a matter of preference (and social anxiety) that I'd prefer a comprehensive guide over a chat room any day.

When I say "root", I mean quite literally the "root" folder that the game starts looking for certain files in. RimWorld will always look in your mod's About folder for the About.xml, the Textures folder for any textures, etc. If you're using LoadFolders it will prioritize looking there for certain files. If you wanted to load certain textures based on the VOID mod being active then you'd just add another "Textures" folder inside Mods/VOID. All of these named folders (Textures, Patches, Sounds, etc) are "root" folders for those file types and they need to be there if you're loading those file types. The wiki explains this via "LoadFolders.xml allows you to specify..." And with any form of documentation, it may read fine for 99% of people and 1% of folks may not get it the way it's presented. We can't make it perfectly clear for everyone, we can only make it as clear as possible for the majority. :/ That's why that channel in the Discord exists. To bridge that gap.

I wouldn't call the Patches folders I added "root Patches folders", considering they're buried within subfolders and not, you know, in the root of the mod folder. This is what I mean about the wiki's documentation being unclear, because the only example of LoadFolder usage is to override the default version foldering. Now that I understand how it works the wiki makes sense, but before now it was very unclear. When I tried adding a Patches folder in the root and putting everything inside, it ignored my LoadFolders entirely and I had to figure out the issue myself.

Just looked at your mod too. Looks like you did add root Patches folders for each mod's patches. That's how it should be and what I've been trying to say this whole time :D So yeah, it should work now so long as your LoadFolders are correct too.

Didn't know you were using LoadFolders, but in any case you still need to use a Patches folder for your patches. Look at my Fireflies 2 mod to see how. I use LoadFolders + Patches folders for each conditional patch for different mods so that only the patches for certain mods are loaded by the game if those mods are active. I'm not sure why you are so adamant on not believing me on this, I even showed you the line of code in C# that makes it so you have to use a folder names Patches. And yes the wiki outlines LoadFolders exactly how it should. If something there is confusing then again, the Discord server is the place to go. We answer questions like this every day. It's the best source of knowledge the community has in terms of modding the game. The amount of accurate knowledge on the Discord server faaaaaarrrrrr outweighs that of the wiki. Glad your issue is fixed though, even if by what you're saying you did shouldn't allow it to work. lol

Okay, I did some messing around, figured out the issue, and pushed an update which should fix it. No idea why it used to work and suddenly broke, but fingers crossed it's stable now.

And for the record, making a root "Patches" folder was not the answer. The wiki really is lacking documentation on the use of LoadFolders.xml, and in my opinion a discord server is no substitute for thorough documentation.

It 100% does matter.

Just because you've seen other mods do it a different way (without a root "Patches" folder) does not mean they are doing it correctly. They are not. Don't use other mods for reference, that's how you get into the bad habit of "cargo coding". What the wiki states is that your patches, textures, new xml files, and sound files can be in any named folder and named file you desire so long as they are also in their appropriate root folders which are... "Patches", "Textures", "Defs", and "Sounds". The info on the wiki about this is correct and it is not blindly giving out bad information. Please head over to the official Discord if you want to know how and more importantly, why, things should be done certain ways or if something is confusing. The mod-development channel there exists specifically to help people make mods.

@Scurvyez Not every mod I've seen uses a Patches folder, and I've had zero issues running this mod for my own purposes without a Patches folder. The wiki page on Patch Operations also states that "Just as with XML Defs, folder and file names do not matter and you can freely name and organize your patch files in whatever manner you wish." so maybe someone should get around to fixing that if it's apparently "blindly giving out bad information".

Caveat to my first statement, even if you use load folders, your patches still need to be in folders called "Patches".