Added Motenten's new XMLs (Idr which were new, but I think SAM, NIN, and DNC weren't up before). He also said his XMLs have all been updated/fixed, so I recommend redownloading them if you've been using them.
Added Motenten's new XMLs (Idr which were new, but I think SAM, NIN, and DNC weren't up before). He also said his XMLs have all been updated/fixed, so I recommend redownloading them if you've been using them.
ok thanks both of you, I'll just ask brd that does march/min or min/min to double march in pug now, need a few more days to work on it then I'll try to post it if I manage to make it work.
Working on a DRK XML atm and ran into an issue with a rule for Aftermath configuration.
This is my Aftermath rule to set TP set to Aftermath.
<if buffactive="Aftermath">
<var cmd="set Use-OffenseMode Aftermath" />
</if>
The variable is getting set, however its not equipping my Aftermath set until I do a manual update or another action taht would cause an update afterwards. Do I need to add another rule elsewhere to trigger an update after Catastrophe to get spellcast to equip the proper gear on Aftercast?
Depends on your XML. Some XMLs automatically update after each action. Others require you to manually do an action.
the XML does update after each action, I'm guessing the aftermath buff isn't up in time to be checked before aftercast.
Could use AutoExec for that if the issue is Spellcast not catching the buff quickly.
It sounds like you want it to be set immediately after the weaponskill, but the rule check is for the buff itself, which won't appear until the after the action has completed. In the case I'd just make the small tweak of:
and put it in the 'First' rules section (it looks like you're using a derivative of one of my xmls).Code:<if Buffactive="Aftermath" Spell="Catastrophe"> <var cmd="set Use-OffenseMode Aftermath" /> </if> <else> <var cmd="set Use-OffenseMode None" /> </else>
The best way to do this is with Autoexec spellcast requires an action to be performed and won't do anything until and action is performed. Autoexec can be set up that upon gain buff aftermath to perform a sc command, as well as when you lose the buff. Or you can just force the variable on aftercast of your weapon skill. Autoexec imho is the best way to do it.
Something like:
<register event=gainbuff_aftermath>sc var set Use-OffenseMode Aftermath; sc set Use-OffenseMode</register>
Montenten, I moved it to the First section, and used the rule you provided. Now, the Use-OffenseMode variable doesn't change at all.
Ehh.... Can you post a pastebin of it? Kinda hard to guess what's wrong.
<if Buffactive="Aftermath" Spell="Catastrophe">
<var cmd="set Use-OffenseMode Aftermath" />
</if>
<else>
<var cmd="set Use-OffenseMode None" />
</else>
This code will only set aftermath on if both aftermath is up and catastrophe is being used otherwise its always setting to none. Unless it defaults to and or condition and I just confused myself lol.
Woops. Right. <if Buffactive="Aftermath" Spell="Catastrophe"> should be <if mode="OR" Buffactive="Aftermath" Spell="Catastrophe">
Also, you have a copy/paste error. Your scythe TP sets (particularly, the Aftermath set) are based on your great axe TP set (which doesn't exist) instead of the base scythe set.
Edit: Also also, your equip rule in the weaponskill section, <equip when="Precast" set="$WSSet|$Mekira-oto" />, should go after the rules to define the $Mekira-oto variable.
Everything works now, just one more question. If I don't have enough TP to do Catastrophe, but attempt the WS anyways it swaps to the Aftermath set anyway. Is there a solution for that or something I'll just have to deal with?
<if type="Weaponskill">
<if mode="OR" TPLT="100" advanced='%SpellTargetDistance>4' notstatus="engaged">
<addtochat color="121">Too far away from target, not enough TP or not engaged. Cancelling WS</addtochat>
<cancelspell/>
<return />
</if>
</if>
You can add another confirmation that your TP is over 100, but that's not entirely reliable since it's possible to issue the weaponskill command before you can actually see your TP hit 100, and it will still fire properly (this is actually something that's part of the ReturnRules include, but usually deactivated because of said unreliability). At worst, hit the manual update command (F12 if you use my suggested alias settings) to force it to realize that Aftermath isn't present, and revert back to the base set.
f12 it is! Thanks again for the help Motenten and Kenshyn.