jarlelin

Not that I've given this too much thought since I find it a pretty unlikely scenario, but letting gcd be affected by haste would be a fairly magical fix that solved most our problems. Then our only problem would actually be the .5 second cast and theoretical human response time in button-mashing.


I am not a big fan of this sort of response but here goes: There are other threads on this forum that deal with optimal castsequence macros. In fact there are allready three very extensive hunter-threads active at the moment. (hunting hunters in public, BM after 2.1, and the hunter mechanic after 2.0/tbc threads) Adding a fourth thread with similar discussion about optimal cast sequences serves no real purpose other than making it even harder to find the information and making the good members of this forum repeat their own work for newcomers every second week.




In short: no, this is wrong, please read on.

The way I model this, though I haven't seen much discussion on it and haven't really gotten it confirmed by anyone yet. Hopefully someone can now:

Your bow has a post-haste attack speed of S.
This gives your auto attack a cooldown C, of S minus .5 seconds.
And as always you have a cast time of .5 seconds on the actual auto shot.

Given S=2.1, C will be 1.6
0s Auto shot is fired
0s+C=1.6s Your auto shot cooldown is finished.
0s+C=1.6s Auto shot is automatically initiated and cast time started without any action required by the user.
C+0.5s=2.1s Auto shot fires and you start again.

It is in the period C that you will want to finish all and any special actions. Any action that stretches out of the C or any action taken between C<t<C+0.5 will halt or refuse your auto shot cast from taking place. Your auto shot cooldown will still be ready though, and it will be initiated on the first available space of time.

So if you fire ss at 0.1s and it has a cast time of 1.2s it will finish at 1.3 and you might even manage an arcane before the 1.6 mark. If all actions are finished before 1.6 and the character is free to perform his auto shot at that time, he will automatically do so and finish it by 2.1 if not haltered in some way. If you however decide to use a KC somewhere in between 1.6 and 2.1 this will terminate the cast time of the auto shot and it will reinitiate at the time the KC is finished. The cooldown will still be ready so all you really need is to allow the 0.5 second cast of the auto shot to restart the cycle.


To reiterate, because I usually lose my way when trying to explain something.
If your auto shot is toggled on it will automatically be performed by your client without any needed action at any time the cooldown is ready. This requires 0.5 seconds of you not performing ANY other action within this period. As soon as the auto shot is fired, this auto shot will be on cooldown for a period of [ "attack speed" - "0.5 seconds"]. This cooldown is the time between shots where you want all your other actions to take place. As soon as this cooldown is done you want your character to be free to perform his auto shot and restart the cycle.


PS. Now go grab yourself some stacked haste to give yourself a 0.95 attack speed and try to even hit an arcane every six seconds within that 0.45 second cooldown period without pushing back your auto shot with real live latency of at least 80ms and some possible minor fps issues. Even that gets fairly impossible.

PPS. Am I misunderstanding the phrase clipping? I always thought that was when you denied the next auto shot of actually firing at all, as in starting the next ss too soon. Meaning you lost an auto in your cycle. Whilst pushing your auto referred to being a tad slow on your ss so that your auto shot was performed some tenths of a second later than it should be.