[Madawc]

Kirschy, on 08 June 2010 - 12:24 PM, said:

A mean of 9.15 hits per WS seems kinda high for Ein? Were you /nin or something?

LS won't let me be anything else! + KC zerg

This post has been edited by Madawc: 08 June 2010 - 12:57 PM

[Kirschy]

Ahh that makes sense~

Since Nameless + Madawc seem to be the ones parsing/trying this out, what would you say your mean Hits/WS rate decreases by?

This post has been edited by Kirschy: 08 June 2010 - 01:27 PM

[Nameless]

It is hard to say since all the events I go as drk involves a little bit of zerg. But I think I went from about 5.00 or 5.10 to 4.80 or 4.90 with an OAT weapon. And also, the time between hitting 100% and WSing before your next hit is greatly reduced, which won't show up on the WS rate, but will shorten the time in between WSs, which IMO is the greatest advantage.

[Madawc]

doing alot of redundant code:

        <if mode="AND" CommandPrefix="/weaponskill" TPGT="99" status="engaged">
				<if Spell="Catastrophe">
					<action type="Equip" when="Precast" set="Cata" />
					<action when="done" type="command">input /ma "Cure VI" Madawc</action> <--- New line
						<if BuffActive="Souleater">
							<action type="equip" when="done" set="SouleaterAftermath" />
						</if>
						<else>
							<action type="equip" when="done" set="MeleeAftermath" />
						</else>
				</if>

edit:
this method is not good either, since the new line that triggers a "check" and sometimes "Aftermath" is not registerd fast enough so the check will put on "non-aftermath" gear. I have seen this in action myself. Another metod is to use a secondary spell that only puts on "aftermath gear" or "aftermath+souleater gear".

if you kill with WS, spellcast will abort the "done" actions and go to idle set.

The best way I think to fix this is the <register event="tp_???">input /ma "Fire V" Madawc</register> trigger to be queued to parse after the /ws rule is done, instead of trying to run ontop of it.

This post has been edited by Madawc: 08 June 2010 - 05:08 PM

[Nameless]

Madawc, did you ever figure out how to fix the after ws gear not swap back problem? or figure out why it does it occasionally?

[Madawc]

1. SpellCast 2.30 will look at what you have equipped and then decide what to put on after an event. Should you have a rule where you want to put on Rajas, but spellcast detects that you already have Rajas on, it will not try to change it, as you will just send a useless command to the server. With some lag your client and spellcast may experiance that some equipment are on but in reality on the server it may be different. So that spellcast does not change that item. This is one problem, you will stand in partial WS gear, partial TP gear.

2. An event may trigger during WS. this will abort the current rules for the WS, and spellcast will jump to the new set of rules.

I think the only way you could work around this is to have a delay after WS and reparse so you don't have to do it manually.

<command when="done">exec restore.txt</command>

restore.txt:
wait 1
input /ma "Cure VI" <name>

Or something like <aftercastdelay delay="3.2" /> or in that nature.

This post has been edited by Madawc: 02 July 2010 - 02:14 AM

[Nameless]

Have you tested the method yet?