Honestly spell batching is so horribly implemented it should be scrapped.
When my pet loses aggro on a mob and I use intimidation (an instant spell with 100 yd range) it won’t go off until the mob runs all the way over and hits me.
I won’t even go into the complete craziness I experience on my mage. I’m sure you’ve heard it all.
He could have all his spells macrod to cast dispells first or have a spam dispel macro that floods the batching with dispells. I’m not sure if you made a macro that cast dispell the maximum amount of characters in one click, if it would interject them as your enemy is casting too. In theory it sounds like it would work, but ive never tested it.
Spell batching is working as intended. Did you think that some 15 year old archaic action processing system would be without downsides? Do you think they spent significant effort to improve the way batching works in retail for no reason?
Spell batching in Classic sucks just as bad as it sucked in Vanilla. Go look at some old bug report forum archives and see the numerous threads from Hunters and Rogues complaining about the same batching related issues they complain about now.
Sadly, this is just how the game works with batching in place. And since they recreated batching on purpose for these exact kinds of stupid interactions, it is 100% intended.
so yeah uh all sarcasm aside, polymorphed players are not supposed to be able to cast spells. if he somehow casts dispel on himself to remove polymorph off of himself, im not sure how that is possible. you say “spell batching” but i doubt it because if there is nothing to dispel, dispel will not be cast even when pressing the button. if dispel is cast, that means polymorph is already affecting the target. maybe you observed what was happening incorrectly?
How would you go about self dispelling? Even macro’d and spamming at the speed of light the dispel wont go off because there is in effect nothing to dispel until the sheep lands.
Spell batching and leeway are the reasons a dead mob can hit you. Spell batching and leeway are the reasons a CC’d mob can land a hit 200 yds away. Spell batching and leeway are the reasons a mob in my ice trap can land a hit.
Spell batching and leeway are the reasons two rogues in stealth, rogue seen for half a sec, cheap shot rogue, lose stealth, they don’t lose stealth, they don’t get stunned by cheap shot.
As someone pointed out this is like intentionally lagging out the server to create a 2004 experience. And yes, trusting Blizzard to create PERSISTENT, artificial lag was foolish. The people who actually know Blizzard did not support this.
You do realize that the game has never existed in a state without leeway, right? It still exists in retail and the formula is still the same. Leeway is another thing that is functioning correctly on Classic.
The only thing that changed over the years was hitboxes being normalized.
While the cast for intimidation is instant, it still requires a “next successful melee hit” from your pet. It’s possible your pet is chasing the mob that you have aggro on and hasn’t had a chance to hit it yet. That wouldn’t be a spell batching issue.