Yes. The priority list for high and low priority batches changed after Vanilla. That change has been reverted from the modern client to a Vanilla-like priority.
If you hadn’t noticed, “Classic” is a modern recreation of Vanilla. The entire game was rolled back to a Vanilla state, minus bugs or inconsistencies of course.
This change in priority follows that same rollback.
So you understand that they made this emulate vanilla. You have been saying this whole time that it is incorrect and needs to have only certain spells high up on the priority (like the change they did in later expansions).
Are you admitting you have been wrong? Because you actually just changed your stance completely.
He’s lonely. Not hard to see why he has no friends so he has to try to take things out of context, spin and attack people to support his own argument.
He already lost a long time ago. We just humor him, at this point.
I really hope they either remove it completely or cut the batch time by 50%.
Right now its an artificial change that isnt accurately replicating how it should be.
For instance, as a warrior if you hit execute it’ll go off but will also consume the rage from your next white hit. So you’re essentially losing out on rage from a white after hitting execute due to batching. That is not how it worked in vanilla.
Another example for pally, pallies spam flash of light. Say you’re spamming flash and go for the divine favor holy light. Multiple occasions if you’re spamming flash, then immediately hitting divine favor into a holy light the flash of light prior to hitting divine will consume the divine, thus your holy won’t crit.
Two game breaking issues with batching there, with many more found. It needs fixed or removed completely.
Lol you two are perfect for each other! Proven both of you wrong on both of your complaints, see the evidence/proof, and then double down on you still being incorrect even though the answer is. literally. right. in. front. of you. This has been very entertaining =D
No. The order is fine, the timings arent. Read the OP again. It’s about the delays to action, unreliability of pets, improper or delayed and sometimes non-existent execution even when an ability went off and triggered a G/CD, etc.
You have been changing what everyone has been talking about this whole time just for the sake of hearing yourself argue that the goalposts you move you are beginning to believe actually took place.
Reread what I and everyone else has been saying.
Priorities may be as they were but the execution is improper due to any of the things I’ve mentioned like feeling as if the command is batched before the execution batch, general delays or sluggishness, unresponsive pets or abilities, etc.
More than likely due to the new batching system trying to “feel” like it did in Vanilla.
Which is why I believe they should ditch the new system and refactor the code so it DOES function like it did in Vanilla since the current iteration is for BFA. Simply changing the “tickrate” won’t have the same effect if how the system executes commands is different from Vanilla.
For the slow: It is programmed for BFA execution with Vanilla timings and priority. It needs to be reprogrammed to how it executed commands in Vanilla.
You’re the guy that literally said
Because changing what Blizzard said to suit your narrative is you proving people wrong.
LMFAO HAHAHAHAHA!
“Yeah so what if I lied about what they said, I proved you wrong by lying about what blizz said” HAHAHAHAHAHA
Now I know you’re just here to give everyone a ride LMFAO!
I knew it. For a while I thought you were serious but now you’re just being blatant about the trolling lmfao!
EDIT:
Holy f-ck your post history 
You’re seriously low on friends around here. The absolute cringe!
I understand what you’re saying. But it’s still incorrect. You are saying that you think certain spells shouldn’t be put on a batch and should be used instantly. Correct? Well I’m referring to this as a priority. Not an inbatch priority but a priority.
This is not how it worked in vanilla. When you said there was no priorities in vanilla this is where it sounded like you were just switching your argument.
There is no spells in vanilla that take PRIORITY over the spell batch and be pushed out of a batch.
Blizzard literally confirmed this in EVERY. SINGLE. PROOF. you have tried to present. Do you understand this?
Imagine judging someone based on the friends they have on a WoW forum. Just imagine that for a second lol.
If i got all the time back i spent waiting for loot to load i couldve levelled another toon to 35
I don’t remember spells acting like this at all in retail vanilla. Batching is seriously way overtuned.
You forgot to say “try again” at the end
Let’s examine what I ACTUALLY said and not what you HOPED I had said:
I.E. - High priority, outside of the main batch. This is what we’ve been talking about and referencing repeatedly. This is why I said the priority is fine - but many of the abilities function as if they fall in the wrong batch - delayed, unresponsive, etc.
Your whole argument is that you read what you want to read and not what is written by ANYONE in this thread.
Don’t try again, thanks for playing. You don’t get to dictate what other people have said. You don’t get to constantly change people’s own words for your own argument.
That’s never how it worked. That might work with the other 10 year olds on the playground but not here, friend.
Imagine being stupid enough to think that saying someone said something they didn’t - which is your ENTIRE method of argument - actually works.
If this is how you are on the internet - real life must be a lonely place for you.
Highly suspect this batching system they put together is also causing a druid issue, the talent furor is supposed to give you energy/rage instantly on shift, but instead its delayed about 1-2seconds.
Seems like EVERYTHING has a delay on it and its causing many things to just not function properly.
+1, I don’t care if this is a “change” or not, spell batching is cancer. Classic is a far cry from the vanilla experience anyway, let’s do away with this archaic crap.
You mean like this?
It’s pretty simple what you think should happen and what actually happens.
It’s just kinda obvious that at some point in this argument you might have found out you were wrong and now you’re just trying to twist and turn this argument into something unrecognizable until you decide you have won.
This isn’t the case.
You think that spells should have a priority like
When in reality it functioned, and NOW functions like
There was no abilities that functioned like you want them to function. You are simply incorrect and I am actually astounded it is taking you this long to admit it.
I’m not sure why you feel the need to continually argue the point, but there are several abilities in-game that do not function as they did in vanilla, clearly. Vanish being a very obvious example, along with FD and Execute. I mained a Rogue in vanilla and never got hit out of stealth after vanish due to batching. It didn’t work that way in vanilla. The hunter issue is probably the most glaring; the playstyle around feign death is completely different specifically because it’s just not working the same way it did in vanilla. Seems related to batching, IMO.
That’s funny you bring that up because that’s one of the main reasons a lot of people were asking for spell batching because they referred to getting rogues out of stealth who just went stealth with abilities.
Another case of ‘I don’t remembers…’ that’s just you not remembering what actually happened.
Sorry, but feign death and vanish both suffered from this back in vanilla. No doubt about it. I played those classes and remember it clearly. Also, people were always moaning about it on the forums back then.
There is no evidence of that ever happening to my knowledge. Do you have any contrary evidence other than hearsay?
Hey, remember vanilla wow? Yup that sure was a fun game, hey you know what would be great for classic? A system that emulated spell and input lag. Gotta get that true vanilla feel