1.12 Mechanics or Server Problem?

[Lyker]

I have noticed a problem that has caused me a little bit of sadness as a Mage. I'm wondering if it's something that really existed in 1.12 or if it's an issue with the server and the way the game is being run. I never encountered this issue in retail, so it was either patched out or Blizzard handled things differently.

On a few occasions I have used Blink (on very low health), usually against a Warrior who just used Intercept. I blink away, die, and see my body teleport back to where I blinked from. Being alive on my end and then being told "oh wait you actually died lol" is pretty stupid.

Naturally, I have not lost a 1v1 to a Warrior here (I'm leveling as Arcane). I simply have far too many ways to control them and they have no chance. This thing has only happened to me in 2v1 or 3v1 situations. Still, I take hits from them that I shouldn't. When using Frost Nova and Cone of Cold it seems that I have to be more precise than I have ever had to be in order to avoid being damaged. When using Blink I have to be faster than I ever had to be.

I believe the reason for this is because damage from melee swings is caused instantly, which never seemed to be the case in retail. Here is a timeline of an example, times are estimated. By the way my ping is normally 125-135.

000ms - Stunned by Intercept
400ms - Warrior is within 5 yards
425ms - Swing hits me but I don't get any feedback
500ms - Blink pressed
600ms - Blink Activates, teleporting me forward
700ms - I receive the damage from the swing and die
800ms - Dead body is moved back to where I blinked from

Here is how it has always worked in my experience before this server

000ms - Stunned by Intercept
400ms - Warrior is within 5 yards
425ms - Warrior swing starts
500ms - Blink pressed
600ms - Blink Activates, teleporting me forward
700ms - Warrior swing WOULD have hit me if I were still there

The problem is the game is saying I should take damage if they are within "attack range" even for an instant. Normally, there is supposed to be some kind of swing time that goes along with the visual animation and sound of a swing.

Does anyone have more of an idea of what I'm talking about? Either the server is having some kind of problem and it disagrees with what is observably happening client side, or melee swing timings were different at this point in WoW's history.

I don't really expect them to fix this, but I wanted to understand it better. I think what it means for me is that I'll have to take melee classes more seriously and react more quickly. That sucks without haste rating, I'm often in the middle of a GCD.

[Alkor]

It's working as intended.The swing timer itself is absolute necessity for melee classes, since animations and sounds lag behind quite a bit (they can't be depended upon).
Generally, if he runs towards you and server decides you're within melee range for even a 0.1 second, an attack happens, and the timer starts counting towards the next attack.

Good luck with practicing.

[cigss]

what is NOT blizzlike if you cs his sheep when be BEGINS CASTING and it hits him yet 1,5 sec later you are still sheeped.

[Lyker]

It's working as intended.The swing timer itself is absolute necessity for melee classes, since animations and sounds lag behind quite a bit (they can't be depended upon).
Generally, if he runs towards you and server decides you're within melee range for even a 0.1 second, an attack happens, and the timer starts counting towards the next attack.

Good luck with practicing.

I played only a Mage from late Naxx (leveling) and began PvPing in BC, and played until early Cata. Never did I experience this situation where melee hit you instantly. Never did I experience a situation where I blinked, died, and had my corpse teleported back. That is unique to this server, and I have played on servers where I had 200ms ping.

If more people think this is what happens then I will accept it. I think it's stupid but I guess I'll just have to adjust my playstyle. I also have to CoC and Frost Nova at the very edge of their range, otherwise I will get hit. Not the case before...

what is NOT blizzlike if you cs his sheep when be BEGINS CASTING and it hits him yet 1,5 sec later you are still sheeped.

This is also really stupid and I have experienced it a time or two with healing spells and Fear on this server. I can tell they are locked out because then they don't cast any spells in that school but their spell still goes through.

[Arucado]

The problem is called DELAY and is not working as intented.

[Snautz]

I played only a Mage from late Naxx (leveling) and began PvPing in BC, and played until early Cata. Never did I experience this situation where melee hit you instantly. Never did I experience a situation where I blinked, died, and had my corpse teleported back. That is unique to this server, and I have played on servers where I had 200ms ping.

This is a massively populated server, you're forgetting to take server side delay into account as well which can be pretty huge on peak hours. The few times I've experienced the corpse teleport issue have all been during the peak hours.

[Koopa]

what is NOT blizzlike if you cs his sheep when be BEGINS CASTING and it hits him yet 1,5 sec later you are still sheeped.

Same with stuns.

Stuns enemy cast > Cast still goes off despite being stunned > Nostalrused.

[Halcyon702]

This is the intended balance to Mage/Warlock Freeze/Fear not breaking on damage as it should

[Colezz]

you cant complain as a mage when i silence u mid poly and i get sheeped

[Lyker]

you cant complain as a mage when i silence u mid poly and i get sheeped

Is this from a Shadow Priest? The spec with the best chance against Mages. At least when you get Polymorphed you aren't being killed, the Mage is just running away because he has almost no chance of winning.