XML re-imports?

I'm trying to maintain my triggers, aliases, etc, in a collection of XML files. I have them broken up into their various groups, so several files, to keep from getting super-huge files that I can't easily examine and update.

Since I'm still in the early stages of writing things and making several changes to the triggers and scripts, I am wondering if it's possible to have some sort of "master XML file" that imports all of my other XML files. What I want is basically to wipe out nearly all of my settings (but not quite everything, as it's just the triggers for curing and defense stuff) and then an easy way to programmatically re-import everything instead of having to go to the menu and the dialog and select the dozen or more XML files one-by-one to be imported.

I had hoped that there would be a script function to accept a filename to import settings, but all I found was ImportXML that takes the actual XML string and no filename option. I'd like to have a script function for re-installing my combat system all at the touch of a button (so to speak).

Any help on this? Is it even possible?

If you are trying to implement switching a combat system on and off using that, then that's not the best way to do it. That aside though - why not write your own function that will accept a filename, read the text from the file, and then pass it on to ImportXML?

I'm certainly not trying to switch the system on and off. I'll do that with a few flag variables.

No, what I'm trying to do is maintain a version of all my settings nicely organized in XML files and be able to import them on other computers or other character worlds or even just to maintain versions of the scripts more easily. Wiping out the settings is easy enough (though it would be easier if it used a hierarchical group structure, similar to folders in zMUD), but importing the settings fresh is difficult.

I had thought about loading the entire XML file into a string variable and passing it to ImportXML, but I'm afraid that even with my splitting up of the settings that such a string would be too large for the system to handle effectively.

There is File > Import, but as far as being programmed, all you can do with it is DoCommand which brings up a dialog.

What about writing a script which uses FSO to write the world file directly. Take a list of files and tack them together in the right order when youre done.

It might be best to keep a couple of files, one for the header (world settings), one for all the triggers, one for all the aliases, etc, (so you can just tack things on the end of the respective files instead of having to insert in the middle, since that would get messy), and then close them after youre done writing (with </triggers> for instance) and then assemble them all into an XML file (which you can then simply open as a world).
Since thats all importing does, and you don't need MC to do anything special with them (except generate a worldID, remember to generate a new worldID).

I've found that the include tag in the world file is very useful for what I'm doing, except that it won't allow me to dynamically update my settings while still keeping the world open. I'll edit the majority of them offline and just make little fixes as I need to, so this isn't a major problem. I'm just glad that I don't need to use plugins with complex interfaces or mash all my settings into one huge world file. Thanks for making such a versatile little client, Nick! Heh.