Weapon Skill Macro Gear Swap

Are you required to call a "Wait" if you were to include gear swapping in your WS Macro?

IE:

Equip body "Loki's Kaftan"
Equip head "Issen Hachimaki"
/ws "Evisceration" <t>

or would there need a wait between swapping gear and the actual call to ws?

It's usually best to add a precast delay, or in this case a small wait, even if it's a small number like half a second or so, just in case in my experience. Due to server lag and all kinds of goofy things like...well lag lag etc I'd rather not be stuck weaponskilling in my tp gear or something silly.

Thank you.

Are you using standard in game macros? If you are, I think I recall that it cannot use waits with values smaller than 1 so if you use a wait you would have to do it for a full second.

Even with SC I've never used waits or delays for this and as far as I can tell I've never had issues. Sanguine blade can tell you pretty clearly if your gear isn't equiping as it's set damage so long as you're fighting a mob with similar stats.

Secondly as far as I understand it, the packets sent out from FFXI are line by line and thus if you lag the cmd to ws won't reach the server before the packet to equip the gear unless you loose a packet or something.

My computer likes to lag sometimes though, and on most spellcasts I've seen in my years of playing, I usually see some sort of precastdelay on weaponskill rules. For instance:
I usually use (as a generic example)
<if type="WeaponSkill">
<action type="equip" set="WS" />
<action type="precastdelay" delay=".4" />
<if Status="Engaged">
<equip when="aftercast" set="HasteTP" />
</if>
<if notStatus="Engaged">
<equip when="aftercast" set="idle" />
</if>
</if>

I mean it's .4 seconds to assure my gear switches when weaponskilling in comparison to not when lagging. This could be a spellcast-onry thing though, directly using macros even when lagging, the game may interpret macro-based gear swaps fully even with lag on either the server or user's side. But since the OP is talking about windower macros, you are able to use a wait of less than 1 iirc. No reason really not to, it's not noticable and it protects against any weird mumbo-jumbo.

My weapon skill rule:
<if mode="and" TPGT="99" Spell="Insert Weaponskill Here" SpellTargetDistanceLT="8">
<equip when="PreCast" set="%spell" />
<command when="PreCast">input /echo ===%spell===</command>
<if Status="engaged">
<equip when="AfterCast" set="TPBuild" />
<command when="AfterCast">input /echo ===TPBuild===</command>
</if>
</if>
<if mode="and" TPLT="100" NotStatus="Idle|Resting" CommandPrefix="/weaponskill|/ws">
<equip when="PreCast" set="TPBuild" />
<command>input /echo Insufficient TP(%TP%). Gear changed to TPBuild.</command>
</if>
<if mode="and" SpellTargetDistanceGT="8" NotStatus="Idle|Resting" CommandPrefix="/weaponskill|/ws">
<equip when="PreCast" set="TPBuild" />
<command>input /echo %target out of range. Gear changed to TPBuild, %spell canceled.</command>
<cancelspell />
</if>

From the OP's post, I saw nothing indicating he's using an alternate macro form, which is why I asked. As far as spellcast goes, I'd like to hear something from the actual devs, to see what goes on behind the swaps but I'm pretty sure spellcast simply outputs them directly to the game.

I don't see any reason not to use a delay if you have sc or script macros but I think their implementation is mainly just paranoia.