I've been messing around with my SCH's spellcast, trying to get it to do a similar conditional check for Sandstorm being up to use Desert Boots as my Idle feet. Since i have my pageup key set to bring me back to my idle gear, what i did is added a "input /ma quake2" to the end of the binding, and set up a part of my spellcast to check for Sandstorm being up and mess with my IdleSet variable accordingly. Just make sure to put in an <action = "CancelSpell"><action = "return"> in there so none of your other rules fire and it doesn't actually try to cast the spell. Doesn't have to be Quake II, any spell you're not able to cast should work fine.
And yeah, autoexec is ugly, I just use it to "cast" Meteor like above to have spellcast run the appropriate keybind scripts for whichever job I'm on.
I know it works, it just misfires on a handfull of occasions. For example if you die in an engaged set, and get raised, the autoset won't trigger until you change states between either resting or engaged. For HBs, I need an aftercast set to be on to have wyrm and wyvern HP gear on, and after that it won't switch to idle again. I haven't figured out a workaround yet.
Does Spellcast automatically add delays when necessary, for example, when equipping a main and sub weapon, or two rings with the same name? And will the full equip swap take place prior to the action? I always get paranoid about how much time it needs to register equipment swaps prior to doing something, in my scripts.
I was planning on making the shift from standard windower macros to spellcast when I finished scholar (because I wanted to have the benefit of the precast for all the fastcast stuff :333 and all the conditional checks because everything scholar has makes it kind of clunky with all the jumping around macros) and this is just in time x)
EDIT: Nvm.
it isnt handling the pauses anymore atm due to not finding best implementation that isnt possibly slowing down the cast of spells it shouldnt be, but in a future ver, maybe 2.31, that wont be required anyways, as i plan a major change to equipment changing.
Your pants will be filled with jizz by the awesomeness that it will be doing. srsly.
and yes basic events will be coming to spellcast in 3.0 - which is still quite a bits away... i want to 'finish' the 2.x series feature wise before moving onto 3.0 which involves rewriting large amounts of code.
RC9 just posted that fixes the bug described on forums in RC8 about menus and shit... left over string termination from when spellcast is in normal mode ><
also fixes some japanese character bug.
Man this is actually really, really nice. Just got home from work and tried it on my wife's char. since she is online atm.
As far as I know about Spellcast works, all you need to do is specify the gear as prespell swap, and it basically intercepts the command to FFXI before it actually gets sent, looks through your XML for any conditions that are met, changes your gear according to conditions, then performs the command you typed in after it's all done. This all happens in less than a second, and you really don't notice any delay at all in execution. I can also verify on the basis of dancer JA's (such as the AF head swap that increases samba duration) that because the way it intercepts the command, it will always swap in time.
I looked through the update notes but didn't see anything about this (or missed it if it was there): last time I tried spellcast it totally screwed up my <st> macros (ignores subtarget or scrolls right through it), so for example if I had a fishing macro like
/ra <stnpc>
/p Fishing <lastst>
it would scroll past the /ra part and go straight to the party chat line. I would have to unload spellcast to use the macro properly.
Is it still this way? All my macros are subtarget, and I don't think I want to learn to play another way this late in the game...
that was fixed a long time ago.
Aikar you are the man.
Spellcast is just win.
I've said it before and I'll say it again. Will you have my babies?
This version broke my old xmls
Aikar when you say it isn't handling pauses anymore does that mean I have to do away with the following code?
Spoiler: show
I hope not