Ximerius, steam has disabled my account with download support... My automatic mod version control system has stopped working. I'll try to figure out what's wrong, so the mods will be delayed in downloading for now.
hey man, hope all is well with you. if you could add these when you'll have time would be much appreciated. Noir's Rilfe Slings, Katanas and Machetes on Back or Belt. thanks
Ximerius, thank you very much for your feedback. I will try to work even more on automating the system for adding mods and updating. Thanks to people like you, I feel motivated again to work with code for uploading mods. Mods have been added at your request and will be updated automatically if the mod is updated in Steam. And yes! Friend! NE ZA CHTO!)
Read the change notes for the latest news.
XML Extensions is a framework and modding tool that is focused on extending the general functionality of XML mods. This includes adding more patch operations, allowing for the easy creation of mod settings, and allowing access to C# variables in XML.
In addition, debugging tools such as improved XML error reporting are also included.
XML Extensions includes an extensive library of patch operations to allow the modder more flexibility in writing patches. These patch operations can make writing XML patches more similar to programming, as you now have the ability to use If-statements, For-loops, compute values, and even write custom methods.
Create mod settings for your mod, only through XML! XML Extensions allows you to implement mod settings extremely easily, and customize your own mod settings menu. You can use these settings to customize values in your patches, toggle patches, or use them in your C# code to do anything else you want.
Settings for mods using XML Extensions are located under "More Mod Settings".
With XML Extensions active, all XML patch errors will now generate a stack trace as well! This means that you can figure out exactly which patch failed, and in some cases, it will even tell you what part of the patch failed. All you need to do is have XML Extensions activated in your modlist while testing your mod.
Here is an example of a trace for a broken patch (you can easily figure out the error is that the letter "N" should be capital in defName):
The vanilla error message for the exact same patch (only reports the parent patch, not the one that actually failed; no clue as to what went wrong):
To use this mod as a user, just load this mod after core but before all other mods that depend on it. As a modder, you need to mark this mod as a dependency in Steam Workshop, and include the dependency in your About.xml.