🛈 Announcement
Greetings! The For Honor forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game
  1. #51
    Originally Posted by CaptainPwnet Go to original post
    You don't really make any valid points. If you have decided that it's safe to GB then does that not mean your opponent likely thinks the same and may also GB at that same moment? So by your logic with my reasoning then you should never throw a GB out ever unless feinting. Even then it's a risk since you can never know if you will be throwing a GB out at the same time as your opponent.
    Well if you just standing there looking at him, walking close toward him of course he would think you're going to GB. But most of the time you should pull it offs when you're trying to pretend you're going to attack or mix up with your combo, and no player would throw GB randomly against that because GB will do nothing against attacking animation.
    Share this post

  2. #52
    I don't understand what all the fuss is about, it's literally a 1,2. When you see the shield, wait for about a second when the animation is the enemy grabbing you, and then initiate your counter, imagine dancing, 1...2...3...4 that kind of timing, remember this and you will literally CGB 80% of the time.
    Share this post

  3. #53
    Allright, thanks <3
    Share this post

  4. #54
    LOL, wow I thought Warlord had a guardbreak bug... I am not a fan of the change. Here's the thing, sometimes I initiate a guardbreak right as my opponent does, and I'll lose for whatever reason (lag, etc...) and normally this would counter each other. I get the reasoning for this, but if they are at the same time, it should counter each other. Not smash it again when a symbol arrives. lol
    Share this post

  5. #55
    yea whichever intern they had that changed it really screwed it up big time.
    Share this post

  6. #56

    No longer child safe

    I'd be surprised if anyone *****ing in this thread weren't light offensive classes. As it was, guard breaks (GB) were so ridiculously simple to counter it was practically a non-move. Imagine if the window for parrying a heavy attack was the full duration of the swing and not just on contact. There'd be no point in using them if you didn't have a guaranteed set up.

    As it is now, on only the second day of full release, shield breaks are still a move with like <10% success on anyone that's competent. If you're near an environmental obstacle that practically becomes 0 because it's expected. If you can't make the adaption you're awful and your complaints about it being broken are merit enough to roll you out onto the curb for the bin men to collect.
    Share this post

  7. #57
    Originally Posted by Claymore1010 Go to original post
    I'd be surprised if anyone *****ing in this thread weren't light offensive classes. As it was, guard breaks (GB) were so ridiculously simple to counter it was practically a non-move. Imagine if the window for parrying a heavy attack was the full duration of the swing and not just on contact. There'd be no point in using them if you didn't have a guaranteed set up.

    As it is now, on only the second day of full release, shield breaks are still a move with like <10% success on anyone that's competent. If you're near an environmental obstacle that practically becomes 0 because it's expected. If you can't make the adaption you're awful and your complaints about it being broken are merit enough to roll you out onto the curb for the bin men to collect.
    It was a none move against good players, yup. It was easy to counter before because the icon matched the time to tech it. This worked out good because guardbreak is spammable with hardly any repercussion. People spam guard-break all the damn time. Only now the defense against the spam has gotten weaker with the more clunky mechanic.

    Also, you sound like a tool. You act like the game is perfect going by what you're on about.
    Share this post

  8. #58
    Completely agree, and even if you counter it the opponent can still spam. You can't punish them normally for it.
    Share this post

  9. #59
    Originally Posted by ExpLiciTSainT Go to original post
    LOL, wow I thought Warlord had a guardbreak bug... I am not a fan of the change. Here's the thing, sometimes I initiate a guardbreak right as my opponent does, and I'll lose for whatever reason (lag, etc...) and normally this would counter each other. I get the reasoning for this, but if they are at the same time, it should counter each other. Not smash it again when a symbol arrives. lol
    My thoughts exactly. If you press the GB in the same time and your opponent did it a split second before you (or due to the lag or whatnot) you are in the bad position. I don't think it should be like this. I really preferred how it was before even if it was a turtle meta.
    Share this post

  10. #60
    Originally Posted by dneemit Go to original post
    My thoughts exactly. If you press the GB in the same time and your opponent did it a split second before you (or due to the lag or whatnot) you are in the bad position. I don't think it should be like this. I really preferred how it was before even if it was a turtle meta.
    What bothers me about GB is that if your opponent does not counter it they get punished but if you counter a GB attempt there is no punishment for it. If I counter a GB I should be able to punish that hero in some way.
    Share this post