Drakedog would tell you how messed up this batching is, I bet.
Just because you don’t like it doesn’t make it messed up. You seem to draw conclusions from your emotions instead of facts.
You know who else does this? Children.
https://www.verywellmind.com/best-online-therapy-4691206
2 Likes
You ok there champ?
Lock’s succubus causing mobs to evade because they’re still “invisible” after attacking is “not even perceptible.” lmao
Batching in vanilla induced behaviors and outcomes based on local and external factors. Classic batching is an artifice that attempts to simulate those behaviors and outcomes.
The issue is not that batching didn’t exist in vanilla. The issue is that Classic’s batching is affecting game play at greater frequency and degree.
1 Like
I’m very happy with spell batching as there are no servers where I play from, meaning I do not get a disadvantage against people who don’t have 150+ ping
What a bunch of crap. They can’t put GM’s in the game, but they can put in artificial lag. They can’t make server pop like it was in Vanilla, but they can put in artificial lag. Blizzard also didn’t bring back 8 hour maintenance, but they put in artificial lag. Oh goody.
Private servers have certainly done a better job with a lot of things, so that’s always a possibility.
No. It’s like walking into a retro arcade and complaining that pacman is getting killed by ghosts half-way across the screen. Then having some self proclaimed expert tell you that’s the way it always played. Here, I have this video.
A lot of people have videos.
Show me vanilla footage where melee hit a mage after they’re frozen and the mage blinked. Show me one where a dead mob gets off an attack after they’re dead and laying on the ground. Show me vanilla footage where a mob is casting, a mage uses counterspell, and the mob continues to cast.
Who were these people that chanted We want lag! We want lag! and expected Blizzard to pull it off successfully?
This is the kookiest thing I’ve ever heard.
My dude, first of all one costs a salary so they aren’t even remotely similar and second of all, there are still GMs. I had one talk to me the other day. I’m starting to think you might not be very old because this is toddler thoughts right now.
Yeah these are REALLY simple thoughts I can’t make my way through the rest of this nonsense. Have fun in school today!
Wait a minute you’re going to have to show ANY of this happening in classic first because of your toddler talk I think something else might be happening here lol. Mobs don’t just continue to cast after being CS’d, I think your toddler brain doesn’t know what a resist is xD
Poor, poor Blizzard. Maybe you should start a GoFundMe for them. Or maybe have them ask the private servers how they managed to have in game GM’s.
And you still haven’t shown me me vanilla footage where melee hit a mage after they’re frozen and the mage blinked. Or one where a dead mob gets off an attack after they’re dead and laying on the ground. Or vanilla footage where a mob is casting, a mage uses counterspell, and the mob continues to cast.
And you won’t because you can’t.
This hits the nail on the head. You can’t recreate something that wasn’t there for some and not a constant for anyone. This is contrived, artificial and a big fail.
Definitely NOT authentic.
1 Like
Show me footage of it happening in classic first, little guy, so I can find one that matches it.
Man the way you were talking I figured you would have hundreds of video proof of this happening. You can’t even find one?
And it does. Classic batching behaviors and outcomes are also based on local and external factors LOL.
You mind being more specific about what you’re trying to say here besides being extremely vague to mask something you aren’t quite sure of?
No it is not. It is effecting it in a very similar way. I have provided proof of this in this very thread at least 6 times.
First of all leeway in vanilla was a mechanic that allowed melee attacks to go off up to about 0.2 seconds after the target had moved out of your melee range. That was to give you a bit of “leeway” to account for the time it took to communicate with servers. Not the case in Classic.
In Classic Leeway just increases your melee range if you and your target is moving. But that’s not working correctly either, and it hasn’t been fixed:
Furthermore, in vanilla the leeway mechanic stopped if you or your target were slowed 30% (walking speed). Not the case and not fixed:
All Blizzard has said is:
I’ve updated the original post in this thread with:
* “Melee leeway” is working as intended.
After careful study and testing, we’ve found that for players with low latency, the state of melee leeway is how they would have experienced the game in 2006.
There are more people with low latency now than there were in 2006, so we expect for some it might feel different, but it is working as expected.
So Blizzard designed leeway totally different than how it worked in vanilla. And they’re happy with that. Of course they are.
And yes dead mobs do attack you - took me 15 seconds to find a video:
Other batching BS:
Go away.
/10char
1 Like
You have to actually log in to that character and play him for a bit before an archived character can be found
Incorrect. I posted a video earlier of a tauren starting and ending his auto attack at an insane range. You literally just made that up. All of that up.
https://www.youtube.com/watch?time_continue=253&v=JYRB2tf5X-Q
@ 4:13 the tauren starts swing and ends swing with the human WAY out of range. This isn’t him starting the auto and then having the human run away. This is how leeway worked. Also here is another example of a warrior landing MULTIPLE autoattacks out of range.
@14:44
These video right here single-handedly prove everything you just said incorrect.
You completely made this up, yet again
@14:44
The rogue is slowed, leeway is still occurring. You seriously think anyone believes this nonsense you are actually making up on the fly?
This video you linked is just leeway activating, this has nothing to do with what I told you to prove. You said mobs were attacking you at max range after you blinked. This is just leeway, my videos above proved it is working exactly like this video.
Next.
This happened all the time, it was just a delay in when abilities actually hit, christ it even happened in pvp check it out here.
Warrior charges and lands MS @4:59, damage and MS doesn’t show up until @5:01. If the warrior were so happen to die within that window the damage would have came up just like the video you shown here. If you need more examples of this on the same video it is RIDDLED with examples. Check when a spell lands, and then see how long it takes for the damage/debuffs to register.
Is there anything else you wanna make up for me to prove worng
Not on warcraft realms. You can find characters you haven’t played or logged into for 13 years or so