Fix or Remove Spell Batching. Period


#68

Thanks for calling me a moron.

There absolutely is a priority. Blizz talked about it in the blue post I linked.

I just linked it. You didn’t read it - but I’m the moron.

Sure, Jan.


#69

And they mentioned they set those priorities to emulate vanilla. As in, making them seem like there is no priorities. Do you understand this?


#70

No. They said they moved spells from high priority to low priority - not “to make them seem like they had no priority”. That is 100% not what Blizz said.

Try again.

If you’re not going to argue in good faith, why are you here?


#71

mobs will still to this day get a single autoattack off on rogues and druids who 1-shot them from stealth.

The thing that made you hostile towards me was an ability that killed you instantly with a single hit, and yous till autoattacked me?


#72

Holy christ child

Do you need me to wipe your butt too?

This is what they said which means exactly what I said it means just with different words.


#73

Read what you wrote out loud. You said it was to make it seem like they had no priority, that is the antithesis of actually having a priority - which Blizz stated they had.

Your excuse is that you used different words which mean different things but to you they mean the same thing.

And you call me a child?

Project much?

I get it, you have no argument so now you are making stuff up and throwing out personal attacks.

That doesn’t phase me.


#74

Let me break this down for you.

Vanilla batching had no priorities. At the very least it had almost none. Right?

They said they are lowering priorities of spells to match 1.12

What do you think they basically said.

Put it together with your own thoughts.


#75

For all the talk of special interrupt code, it directly contradicts what the Blue post said.

Kevin has mentioned that he doesn’t do code. I won’t be surprised if he had gotten that wrong. Your video also doesn’t state when the special interrupt code was added so it’s possible that Kevin is 100% correct but the interrupt code was added in BC or later then removed once they got spell batching more responsive - i.e. responsive enough to match/surpass the special interrupt code.


#76

That’s not what they said at all. You can’t just make up what you THINK it means - what Blizz meant is what they wrote. Which is the antithesis of what you are CLAIMING they said by putting your own failed attempt to ram your own wrong point by twisting words to wiggle your way out of not reading what was linked.


#77

The video was taken out of context I believe. Because they DID change it to the priority list eventually.


#78

Not in Vanilla. After Vanilla, yes.


#79

What are you talking about that’s literally what they said. They straight up said they are changing the priorities to resemble 1.12. 1.12 had no priority list. They changed it to emulate no priorities.

How are you not making that connection.


#80

It’s garbage. Just like #NoChanges. The game will die this way.

Working as intended, even though it’s a worse system.


#81

That true. It’s also possible that the high priority loops are the very special interrupt code that Kevin is talking about - he wouldn’t the technical term for it because he isn’t in the programming department.


#82

Wait a minute so now you’re saying that vanilla didn’t have a priority list. What argument are you attempting to make here now? You are asking for certain spells to not be batched but then you are now saying there shouldn’t be a priority list.

WTF is going on in your head child.


#83

You are so wrong. I played 450 days on a warlock in vanilla. I think I remember how it worked.


#84

Yeah going to go ahead and say no you don’t. Unless theres some video evidence you got then your word means nothing. They know spell batching was on a 200ms tick. They set it up to emulate a 200ms tick. Not really much to think about.


#85

The emulation is not accurate.


#86

prove it…


#87

The hundreds of bug reports related to it might be a hint. Keep your head in the sand, though.