Quote Originally Posted by LilimoLimomo View Post
Can you clarify whether by "over and over again" you mean once per cast, or mashing repeatedly?
Once per intended cast. (You specifically complained about mashing buttons in the original post. So, why would I mash the buttons?)

This is covered in my first post. When using programmatic queuing, macros will have a shorter queue window than normal actions. Because of this, the timing of when you press them is different. That needs to be taken into account when performing this experiment. Naturally if you press any button outside of the window it's capable of queuing in, you're not going to get the results you're after.
And this is exactly why your striking dummy demonstration is of limited value.

In the heat of actual combat, the larger window of time in which I can push a button and expect it to go off is of immense value, especially when I refuse to push more than once per intended cast, because the larger window means I can be less precise with my timing. Furthermore, tossing in macros means I have to remember that my buttons now have three different windows in which they can be pressed (GCD, oGCD, macro).

Hopefully these explanations can provide the guidance you need to give the test another go by performing it the way I did! If it helps, there's a visual effect that happens on the crosshotbar when a button is pressed, so you can watch my video to get a better idea of when I'm pressing the button.
I already did.

Anyone can consistently get the timing correct when there's nothing else going on and they're interested in only a single button. It's like the old meme, "Assume a frictionless, spherical cow."

It's great in the classroom or laboratory, but what matters is how it translates to the real world, to actual combat.