
Originally Posted by
cdgreg
pastebin
Thank you for linking it.

Originally Posted by
Yugl
Code:
<group default="yes" name="Pld|Pdt|Mdt">
My guess is that this group prioritizes MDT as the group? Try moving MDT to the left and see if that affects the XML.
It seems that way, doesn't do this with my NIN SC, I'll figure that out.

Originally Posted by
Yugl
The rule says to set the variable, but they don't say the value to set. So you're saying set PDTIdle to (blank), so no value is set.
Code:
<if spell="Trigger2">
<addtochat color="121">----------------- PDT SET EQUIPPED -----------------</addtochat>
<command>sc var set Grp Pdt</command>
<if status="idle">
<command>sc set PdtIdle</command>
</if>
<else status="engaged">
<command>sc set PdtEngaged</command>
</else>
<cancelspell />
</if>
sc set setname forces the named set to be equipped. It is close to the var cmd which is why many ppl get confused with it.
What this trigger does is set the var to that group and within that group based on the status equips the proper set.
Combined with:
Code:
<!-- BEGIN Status Set Rules -->
<action type="equip" when="idle" set="$GrpIdle" />
<action type="equip" when="engaged" set="$GrpEngaged" />
<!-- END Status Set Rules -->
Makes it so I manually choose which Group I want until I use a different trigger which changes the Grp Var and the Group set.
I hope that makes things clearer Yugl as I appreciate any help with this.