BST XML Help On Engaged Set

Don't use if/if/if/if/if unless they're actually distinct conditions that could all happen at once. For cases where you're doing something like checking which JA/spell you used, if/elseif/elseif is faster, because as soon as one triggers, the parser can ignore the rest of the conditions, resulting in a faster execution time.

Don't duplicate sets you inherited. You inherited them for a reason.

Don't put subjob specific code in the rules section. Groups do this better and cleaner.

Don't inherit/use baseset unless you need to. Spellcast is good about not switching things that don't need switched, but you shouldn't rely on it, and if you inherit the wrong thing, you'll be needlessly swapping gear that doesn't affect what you're doing.

I kept the 'whm sub is always in "standard" gear' logic, even though I don't care for it. You can always change it if you like, but that doesn't belong in rules. The way I implemented it was to make the "engaged" set on whm the same as the "standard", which essentially does the same thing.

Took out a variable or two that was only in one place and wasn't being set anywhere.

You now default to ninja sub's group.

I moved the job specific type sets (waltz, etc) out of their job specific groups and into the main inherit, because if you change subs without changing spellcast group, you won't get what you expect (your gear to change)