WoW Classic Hotfixes -- Updated November 16

[Juggs-mankrik]

Any word on looking into Warrior Execute being double batched?

Execute trigger delay is doubled compared to vanilla

Some background first; the way Execute works in vanilla and classic is in two stages. When you cast Execute the damage of the skill is calculated including the excess rage, the cost of the skill itself is deducted immediately (15 rage untalented), the Execute damage is applied at the next batch tick and then a server-side script runs which after a delay reduces your remaining rage to 0. Additional bug reports from warriors indicated that any rage generated during this trigger window is lost once…