This is either a bug related to guardbreak or something | Forums

[SabunoHakia]

I attacked with guardbreak WAY, WAY BEFORE the enemy but the instant moment they started swinging the weapon it looked like they became immune to the guardbreak and hit me and I bounced off only to watch them hit me when I clearly guardbreak them before they even attacked this has happened mostly on orochi and valkyrie which I will be very clear I save video and check back before coming to make a post.

This actually happened twice with the same player in different situations. I don't know. I can't imagine they are walking left I go to guardbreak and then all of a sudden there are powering though my guardbreak with a single light attack and then the second time it happens it was a heavy.

[Lord.Warden.]

It's all about timing. And some characters like Conqueror for example, if you try to feint your heavy into GB and he goes for a parry, your GB won't work. His heavies can eat through your GBs. I believe it's the same case also with Centurion.

[Klingentaenz3r]

GB is a 400 ms move. Means from start until it connects it's 400ms. Here is a list from reddit to show you why some heavies are easily guardbroken and others are not:

Heavy Type

0-700ms -> 0-100ms Guard Break vulnerability window
800-1000ms -> 0-400ms Guard Break vulnerability window
1100-1300ms -> 0-600ms Guard Break vulnerability window
1400-…ms -> 0-800ms Guard Break vulnerability window

Light attacks beat GB. You can almost react to attempts with them. There is a 100 ms vulnerability on startup but it is really very very slim. So basically if you get caught with a gb when you wanted to throw a light you probably were just a notch too late. Bashes of course also beat GB attempts but GB can beat those if initiated early enough when they are about to dodge to activate the bash. Works well on warden for example. Conq's activates too fast.

GB that interrupt GB is a bit of a strange thing. It might be that the other guy was just a little faster with the input and due to latency you get this result. Could be also that in general the later thrown GB just overrules the other.

There you go. This is the reason you can gb some heroes basically right after feinting your own attacks on their heavy start up and some not (those only if you threw a gb way earlier and they reacted too late and hence you land the gb in the 0-100 ms window).

If you are looking for the specific character data google "Damage values For Honor" or use this link https://docs.google.com/spreadsheets...gc/edit#gid=0] You'll find the attack speeds in the related tab

feint into gb is now 300 ms btw and made it more consistent against most heroes and also improved all kinds of unblockable mixups, but attacks with 100 ms vulnerability still trump those most of the time AFAIK

[SabunoHakia]

Thank you I will take a look in to this on the video and see if I can replicate the way this happened. But based off the screen I attempted to guardbreak and it looked as if it was ignored entirely and they just attacked. This wouldn't shock me if it was just a small error in a few things as I recorded my gladiator being pinned against a wall and then, having a seizure and then just being killed as I could not move. But this is appropriated.

[Klingentaenz3r]

be ensured that we are 100% sure that this is a gb vulnerability thing btw your glad has also 700 ms heavies and hence can answer gb attempts with it (read as read). two patches back he could even zone any gb on reaction due to him having 0 ms GB vulnerability on his zone.

Keep in mind that there is always latency between you and the opponent and therefore sometimes it can seem that you should have already connected but then it bounces off. It always depends on when the other side made the input and when you actually connect with your attack.

[SabunoHakia]

Will do and thank you.