🛈 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. #1

    fix your ****ing character selection

    Twice in a ****ing row I tried pick a character and it kept reverting to lawbringer. I manually clicked 'Confirm' after selecting my loadout and confirmed it showed Conqueror yet the load screen it switched to lawbringer.

    Make that three times...


    Yeah so during Brawl, the third time I went into the confirm, cancelled, confirm, cancelled just to be so sure the conqueror was showing before pressing confirm. I pressed it, it zoomed it....BOOM! it switched. During any game where I can select feats, it will switch character because in duel/brawl it by passes that confirmation and I can not switch character.
    Share this post

  2. #2
    i honestly don't think they even knew this issue existed, iit almost always happens to me because of brawls. I contacted their live chat yesterday and sent them this video as proof https://www.youtube.com/watch?v=lbXHkMSgOx8 so lets hope they can figure out a fix
    Share this post

  3. #3
    There's an easy solution;

    Note, that in the first case you had the Valk selected. then you confirm the Warden. But as you can see, the tick on the Valk's picture doesn't disappear! Thus, there are two pictures with a tick, the Warden and the Valk. What you have to do: Pick the Warden once, then cancel the choice, pick him again. Then the tick should only be at the Warden and you will pick him as a character.

    Had the issue as well, it's weird but if you know it, it's easily handled. Still annoying bug though...
    Share this post

  4. #4
    Originally Posted by Gammony Go to original post
    There's an easy solution;

    Note, that in the first case you had the Valk selected. then you confirm the Warden. But as you can see, the tick on the Valk's picture doesn't disappear! Thus, there are two pictures with a tick, the Warden and the Valk. What you have to do: Pick the Warden once, then cancel the choice, pick him again. Then the tick should only be at the Warden and you will pick him as a character.

    Had the issue as well, it's weird but if you know it, it's easily handled. Still annoying bug though...
    I tried that, it doesn't always work. I had this happen before but got around it like you said but in this case, it didn't work. As I said, I kept checking it.
    Share this post

  5. #5
    For me, that solution always works. Just make 100% sure, that there's always only one hero with a tick, worked 100% for me though. Sorry for you, if it doesn't :/
    Share this post

  6. #6
    Originally Posted by Gammony Go to original post
    There's an easy solution;

    Note, that in the first case you had the Valk selected. then you confirm the Warden. But as you can see, the tick on the Valk's picture doesn't disappear! Thus, there are two pictures with a tick, the Warden and the Valk. What you have to do: Pick the Warden once, then cancel the choice, pick him again. Then the tick should only be at the Warden and you will pick him as a character.

    Had the issue as well, it's weird but if you know it, it's easily handled. Still annoying bug though...
    I'm not saying you are wrong, but he doesn't have Valk recruited so it shouldn't have locked her in the first place.
    Share this post

  7. #7
    I never had this issue on Xbox is this a PC only bug? Or is there anyone on PS4 or Xbone that has had this problem?
    Share this post

  8. #8
    It could be a PC only bug because I only seem to have the issue this bad when clicking to confirm. Using the controller has always been more successful.

    And jsut to make this clear to everyone, yes I know of the work around and I have done it before (I posted about it before here). But in the case I am referring to in this post, that didn't work. I went to the confirmation and cancelled a total of 3 times in a single match start up before actually confirming and it bugged out still for the 3rd time over the span of 30 minutes. I made sure to let the bug happen several times to ensure it wasn't a once off and that the work around in fact didn't work around anything.
    Share this post

  9. #9
    The devs really need to know about this. Hopefully they'll see it.
    Share this post