Spellcast/xml Question

I name my XML after individual jobs, ie NIN.xml, COR.xml. Whenever I change jobs, spellcast will auto load the correct XML to match the new job.

I think if you run multiple characters on be same machine, each with their own XML, you need to be more detailed in the file name, like vize.drk.xml. I'm not 100% sure, since I only run XML on my main

Vize_drk, Snprphnx_drk, arcalimo_drk, arcalimo_blu, etc..

Not sure if the vize.drk format would work, but i know for sure that it does with _

Rename your xml to be Vize_DRK.xml
and when you work on your warrior file, name it Vize_WAR.xml. You shouldn't have any problems as it auto-loads for you when you change your jobs between DRK and WAR.

If you want to be even more specific, you can add a subjob to filename. Such as Vize_DRK_WAR.xml which will be loaded under those main/sub conditions only, otherwise if you sub /SAM or whatever and you don't have a file specific for that, it would load your Vize_DRK.xml

To manaully load any spellcast file, in case you ever wanted to know, just bring down the console (insert button in most cases) and just type in sc load <name of the file>

GL~

For loading a file you can also just type in to the chat window: /sc f file(doesn't need the extension either)

This reloads the current xml:
/sc r

this puts on a certain set:
/sc s setname

and the best one removes everything you're wearing:
/sc n

These are what I use the most in troubleshooting and editing xmls.

You can also create a folder per character and put the XMLs in it.

There was some way to even take it down to XMLs per subjob I think.

Spellcast, iirc, autoloads xml's like this:
Name_Job.xml > Job.xml > anything else you load using autoexec or any other way if it can't find the previous two

so if you're running multiple characters on one computer, best way to label is Name_Job.xml and you should always get the correct one loaded ^_^ <3


Idk if creating a folder per character would work. I've never had to try that though.
The only way I can think of for working per 'subjob' would be in autoexec something like this: