Please change the Volcano map

[Valence]

I don't understand the logic behind complaining about an ability that kills you during your guard animation. You'd have been dead all the same if the damage had been instant.

This actually introduce some tactical delay where you can heal, do certain things in a pinch, etc. If anything, the design of the netcode and how mechanics behave makes more sense in pvp than pve to me.

[Arohk]

I don't understand the logic behind complaining about an ability that kills you during your guard animation. You'd have been dead all the same if the damage had been instant.

This actually introduce some tactical delay where you can heal, do certain things in a pinch, etc. If anything, the design of the netcode and how mechanics behave makes more sense in pvp than pve to me.

when a Machinist uses his LB on you and you try to use guard to block it, it never works, you count as hit in the exact moment the Machinist pushed the button, even though you take damage two seconds later.
You can use two heals before getting hit by the Machinist LB to survive but guard doesnt work? lol

[Valence]

when a Machinist uses his LB on you and you try to use guard to block it, it never works, you count as hit in the exact moment the Machinist pushed the button, even though you take damage two seconds later.
You can use two heals before getting hit by the Machinist LB to survive but guard doesnt work? lol

It's not consistent Valence. Different abilities get through because of when the damage registers in the animation which isn't the same from ability to ability. And I'm also not talking about being killed while guard is engaging. I mean you are fully in the bubble then die anyway.

It's the same for every damage ability, it snapshots at activation, and the damage resolves later after animation. If anything it's extremely consistent in how it's designed.

That's exactly my point, if the damage was instant, guard would still not work (because you'd be dead, else you'd have activated it before the enemy pressed the button, which is not the case here in both scenari), and on top of it you wouldn't even get the chance to get clutch healed in between. I'm not totally sure how it's any better.

Now then if your solution is to add a long ass cast time to every big damage ability to be able to notice it and guard before it gets used, or to make the damage snapshot only at animation resolution... That's another debate (please no, that would never work at higher level, what a nightmare). People need to stop seeing Guard as a block button. Guard has many uses, be it a tempo button after being bruised, a denial button to prevent getting targeted by smart players or to just soak damage from players not paying attention, and many other things, but it's not a reactive block/parry button to be activated to block something, since most somethings are instant anyway, so unless you actually read people's minds, odds are you're not gonna activate it before they actually use their abilities.

Could Guard benefit from being a little less sluggish? Sure, but ultimately that's not gonna change anything, every ability that registered before you guard will still go through all the same, and with reason.

[Elfidan]

I don't understand the logic behind complaining about an ability that kills you during your guard animation. You'd have been dead all the same if the damage had been instant.

This actually introduce some tactical delay where you can heal, do certain things in a pinch, etc. If anything, the design of the netcode and how mechanics behave makes more sense in pvp than pve to me.

It's not consistent Valence. Different abilities get through because of when the damage registers in the animation which isn't the same from ability to ability. And I'm also not talking about being killed while guard is engaging. I mean you are fully in the bubble then die anyway.