I don't see the point of the new functionality to create additive mods

[CodesbyRobot]

I don't see the point of making a proto_mods file that is empty. It would be better if maybe:

The file also contained 1 example illustrating how to use it (merge, remove, add) and perhaps it could open, upon creation, as another side bar next to "Export Root Directory", like the other two sidebars "Root Directory" and "Bar File" (they could be made collapsable with a middle arrow showing to uncollapse). In that case, the newly opened file on the new side bar would be editable so I can work within the app, checking directly the proto file on the side as well.

[CryShana]

Yeah, I was also thinking of providing an example for each additive mod, specific for that file, though I have not decided yet on what. For now it saves me time of not having to remember what naming it uses and what the root XML element is. Maybe I should also add an icon/indicator to show which entries support additive modding - to quickly spot them at a glance?

As for another side panel and editor all within the same app - was considering that as well... I am unsure yet how I would do the new layout to contain all that without it being too cluttery...

Definitely something I will consider more in the future

[CodesbyRobot]

[CryShana]

Thanks for the help.

How would the user select what exported file to view? Would it be automatically selected based on selected file from left side? Or would you have another side panel for all exported files?

[CodesbyRobot]

In this example, it just opens the file on the side when you click Create additive mods, so you have the references ready. You could make it the same behaviour if i click Export, although if i am modifying the entire xml and not just testing small additive mods, i might use an editor with more features.