Since this mod has been reported working in 1.6 I added it to the No Version Warning-mod
https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=2599504692

This is exactly the issue described in description of this mod. Yhe only workaround is to find this extra "e" in the original xml and remove it. Also you probably should report the typo to the mod developer

Looks like there is an issue with too many records.
At line 1 520 489 the .xml breaks: https://imgur.com/a/2KFvloI
It is not an issue with VSC (I checked other editors).

amazingly, still works. thank you, this mod is a must-have for my purposes

ah, found :D

I use this mod a lot to have a *final* xml export after all patches are applied.

Btw, do you mind to share sources maybe?

godspeed, thank you! this mod has helped me troubleshoot my mods so much

1.6 - still works. Somehow.

1.5 works

can confirm it still works

There was no changes even fr 1.3, I just updated it to mark compatible. The binary is, in fact,. compiled for 1.2.

It doesn't contain any gui references (which Ludeon breaks every single release). All of GUI is done by RWLayout lib (which does breaks every time), and I updating it for every game version.

...and it keeps on truckin'. Compiled for 1.3, working fine on 1.5, crazy.

great mod

still works in 1.4 (thank god)

Is there anyway to make Rimworld load up the unified xml file after it is built once, instead of having to re-create it each time it loads. Can I load the game with say 100 mods, it create the unified xml file and then next time I load up the game, it loads the unified xml file instead of re-creating it. Even better would be to compare current mod list to the one in the unified xml and just patch the new mods added or changed. Said changes to the game would make such a huge difference in load times. Do you know of any project or plans for that?

Works very well and saves my sanity when writing XML patches and the console displays worthless errors.

Thank you very much

I found out that is a feature. If you setup current working dir, you can programmatically change where Unified.xml file be created. That even makes things easier for me to work with. I am going to change cwd to [megamod]/Defs, then Unified.xml file be created in [megamod]/Defs/Mods. No need to copy it. It will work out of the box.

Well, it should be working no matter that. Probably I should use diffferent way to define path. Relative paths have advantade of working without any special effort, but can be not reliable without full control of envirement

You were right on that, sorry for disturbing you. Didn't setup working directory.

You might be right on that, will check that out.

I would argue, this is RimPy issue: looks like it changes RimWorld's current working directory, which makes relative paths to point to incorrect locations.

As a workaround, go to mod settings and change xml export path to absolute one.

My bad, it works as it should. But I have issues when loading from RimPy, I get:
[UXE] Exception thrown during xml export: DirectoryNotFoundException: Could not find a part of the path "H:\Rimpy_dev\Mods\Unified.xml".
It tries to save Unified.xml file in wrong folder, but works fine if I load it from Steam.

I am working on a tool that merges all mods in one megamod in hope to save some loading time. I have tried to use this mod to export data, but seems like game fails to load Unified.xml file if I put in empty Defs folder. Am I right about that? Is it technically possible to import that Unified.xml file to skip XML tree building?

sounds amazing, will check it out!