Hi Aaraa In 2.1.02 Priority didn't work and it executed as Sequential. Ie they were both doing the exact same thing when they weren't supposed to. This was corrected in 2.1.03 and is now working as it is meant to. Having said that it is not genuine Priority. It is a mathematical weighting. It executes with no concept of spell success or failure as once it knows that it can then not act any further. Priority will not always be the correct choice for a macro and In Your case if I am understanding what you are saying Sequential out performs Priority in your situation. This is a valid response. In Priority to get to chaos strike on The last cycle it will take up to 15 keypreses. With Sequential it may be the next option or at most 5 presses. The trade off of using Priority is the burstiness. It runs 1 12 123 1234 12345. The whole point of priority is that it will try Fury of the Illidari 5 times before trying Chaos Strike once.

What you are seeing here is the 15 key presses * 135ms before it gets to try Chaos Strike. If you want to adjust this And stay with Priority then you may need a faster spam rate than 135ms. It's just that blade dance comes available (9th press * 135ms) before it's gotten to Chaos Strike and then 5 presses later it's cycles to Chaos Strike and it's available. Does this make any sense? TimothyLuke

Hi Tim, Thank you for the quick response. Yes, this make perfect sense from what I was seeing. Out of curiosity, I adjusted the macro to a 50ms spam and using priority with the latest update, it appears to be around 450 dps using my macro. As you said, it was cycling through the macro too slowly at 135ms. Keep up the great work! Todd From: Timothy Minahan Sent: Thursday, August 31, 2017 9:04 AM To: TimothyLuke/GnomeSequencer-Enhanced Cc: Aaraa; Author Subject: Re: [TimothyLuke/GnomeSequencer-Enhanced] Something changed (#349) Hi Aaraa In 2.1.02 Priority didn't work and it executed as Sequential. Ie they were both doing the exact same thing when they weren't supposed to. This was corrected in 2.1.03 and is now working as it is meant to. Having said that it is not genuine Priority. It is a mathematical weighting. It executes with no concept of spell success or failure as once it knows that it can then not act any further. Priority will not always be the correct choice for a macro and In Your case if I am understanding what you are saying Sequential out performs Priority in your situation. This is a valid response. In Priority to get to chaos strike on The last cycle it will take up to 15 keypreses. With Sequential it may be the next option or at most 5 presses. The trade off of using Priority is the burstiness. It runs 1 12 123 1234 12345. The whole point of priority is that it will try Fury of the Illidari 5 times before trying Chaos Strike once.

What you are seeing here is the 15 key presses * 135ms before it gets to try Chaos Strike. If you want to adjust this And stay with Priority then you may need a faster spam rate than 135ms. It's just that blade dance comes available (9th press * 135ms) before it's gotten to Chaos Strike and then 5 presses later it's cycles to Chaos Strike and it's available. Does this make any sense? TimothyLuke

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.