AutoExec (2.7) is a plugin that monitors for 'events' in FFXI such as login, logout, changing jobs, day change, weather change, time change, moon change, buffs wearing and being gained, and more. AutoExec (2.7) will give you the ability to configure Windower commands that will be run upon the trigger of these events.

You can configure Windower to automatically load your White Mage macros any time you change to white mage, and load thief macros as soon as you switch to thief, without needing to manually execute the script files yourself or change in game macro books yourself.

It enables you to load plugins and such upon character login.

It's also very useful for loading 3rd party programs upon login to certain characters when combined with the Run Plugin

Upon plugin load, /windower/plugins/autoexec/autoexec.xml will be parsed to automatically register commands. If this file does not exists, it will automatically be created for you.

These commands may be issued by typing //autoexec <command>

autoExec XML files have 2 tag names it expects to see, <register> and <import>

<autoexec>
   <import>common.xml</import>
   <register [attributes]>[command]</register>
</autoexec>

Attributes:

• REQUIRED: Event - What Event to run this command on Example: <register event=“login”>echo logged in</register>
• OPTIONAL: ID - Specify an ID to use instead of automated.
• OPTIONAL: RunOnce - Specifies if this command should be automatically unregistered once its been ran. Supported values for “true” is: true,t,y,yes
• OPTIONAL: Silent - Silences the register and unregister messages for the command. Great for making console less spammy.

Data: The data contents of a <register> command is the Windower command that should be executed. <register event=“login”>CommandToExecuteHere</register>

the <import> tag does not have any attributes, and the Data for it is a filename located in the autoexec folder to import additional commands from. <import>common.xml</import>

All Event names support Windower Plugin Wild Card & Regex Parser, example shown below:

Example commands (console/scripts):

autoexec registeronce login echo LoggedIn;load Plugin;LoadPlugin;
autoexec register jobchange_whm/* exec whm/whm.txt;input /echo == WHM Macros Loaded ==
autoexec register jobchange_war/nin exec war/warnin.txt;input /echo == war/nin Macros Loaded ==
autoexec register jobchange_war/thf exec war/warthf.txt;input /echo == war/thf Macros Loaded ==
autoexec register jobchange_nin/*|jobchange_???/nin .run -kill apps/shadowcounter.exe;input /echo == Shadow Counter Loaded ==

You can use registerq instead to make it quiet (silent) also and not print register/unregister messages)

You can see the | separator on last one, specifying to run on BOTH those events. ??? means any 3 characters, so in other words main job does not matter, anything with sub nin (I believe * wildcard matches everything after it and cannot be used in the middle, unsure, so use ???)

You may do //autoexec list OR //autoexec list echo to view all registered events. If echo is not specified console is used. (you may need to use echo if you use too many that scroll past in console)

All registered events are assigned an ID#. You can do //ae unregister 3.

Where 3 would be the ID# to unregister shown in //autoexec list

When registering a new event trigger you may also specify which ID to assign it too – outside of the reserved zone at least. ID#'s 1-9999 are reserved for automated ID's, so you may do the following:

//autoexec register 34533 login input /echo Logged In!

Then that event will ALWAYS be on ID 34533. I will setup a thread upon release for authors of scripts to list ID's they used in scripts so no one uses an ID someone else is using for their scripts (to prevent problems with people making scripts un/register things. Valid id's go up to 65000.

AutoExec.xml

<autoexec>
   <import>plugins.xml</import>
   <register silent="true" event="login">drawdistance set 10</register>
   <import>JobChange.xml</import>
</autoexec>

Plugins.xml

<autoexec>
   <register event="login" runonce="true">load expwatch</register>
   <register event="login" runonce="true">load spellcast</register>
   <register event="login" runonce="true">load drawdistance</register>
</autoexec>

JobChange.xml

<autoexec>
   <register id="23443" event="jobchange_whm/*">exec whm/whm.txt</register>
   <register id="23444" event="jobchange_blm/*">exec blm/blm.txt</register>
   <register id="23445" event="jobchange_rdm/*">exec rdm/rdm.txt</register>
</autoexec>

This is essentially:

<autoexec>
   <register event="login" runonce="true">load expwatch</register>
   <register event="login" runonce="true">load spellcast</register>
   <register event="login" runonce="true">load drawdistance</register>
   <register silent="true" event="login">drawdistance set 10</register>
   <register id="23443" event="jobchange_whm/*">exec whm/whm.txt</register>
   <register id="23444" event="jobchange_blm/*">exec blm/blm.txt</register>
   <register id="23445" event="jobchange_rdm/*">exec rdm/rdm.txt</register>   
</autoexec>