🛈 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

    conqueror stunlock till death counter?

    how to stop the chain? or is it really 1 hit kill?
    Share this post

  2. #2
    Vordred's Avatar Senior Member
    Join Date
    Feb 2007
    Posts
    533
    umm what chain, i play the conq regularly some would be interested to know about this.

    if you are referring to the Heavy - Shield bash - Heavy, that heavy after the shield bash is blockable. and almost they will run out of stamina real quick spamming shield bash
    Share this post

  3. #3
    Originally Posted by Aksullero Go to original post
    how to stop the chain? or is it really 1 hit kill?
    Sidesteps into hits. freewin
    Share this post

  4. #4

    I tried it with one of my friends. If you have a latency that's sltightly over 35ms you won't be able to get out of the conquerer Stunnlock, Dodges won't go off, the same goes for rollign out of combat.
    Since the devs seem to assume everyone has a perfect connection (well in germany we don't). So I basically fail once/lag too hard and I am trapped until I die. Afterwards the conqus always spam how great they are... well the not thinking about latency with very small reaction times is just one reason why this game sucks and all overly fast or dodgy classes will faceroll you easily (orochi, nobushi, pk) and stunlock classes will do what they do best: stunlock (it's also really frustrating that the conq can spam his unblockable shield bash about thrice in a row I guess.... spaming of attacks should be a no go, always as well as stunlocks)...
     2 people found this helpful
    Share this post

  5. #5
    Dodge the shield charge, you can't do anything on the follow up attack because you are stunned. The chain is then broken.
    Share this post

  6. #6
    Heavier heroes can survives the entire chain until the Conq runs out of stamina. No idea about the smaller classes though.
    Share this post

  7. #7
    Originally Posted by JibletHunter Go to original post
    Well, I can tell that you didn't read this whopping 1 page of text before posting. How does this address the many players with latency issues who are stuck forever?
    Don't buy MP titles from Ubisoft again when they never use dedicated servers.

    It wouldn't be conq problem either, you'd be stun locked and prevented from blocking all classes etc. In fact if you are claiming lag is that bad, why are you playing, you would get owned by everything all the time.

    Thinking more along the lines of a l2p issue.
    Share this post

  8. #8
    Reign's Avatar Senior Member
    Join Date
    Apr 2009
    Location
    Texas
    Posts
    573
    Originally Posted by secrecy274 Go to original post
    Heavier heroes can survives the entire chain until the Conq runs out of stamina. No idea about the smaller classes though.
    Most can I only get off three heavies/bashes before needing to regen. But people are wising up an dodging it alot more than they used to unless I have them against a wall. For the people with "latency issues" the only advice I could give is parry, stop the train before it leaves the station.
    Share this post

  9. #9
    Originally Posted by Banicks Go to original post
    Don't buy MP titles from Ubisoft again when they never use dedicated servers.

    It wouldn't be conq problem either, you'd be stun locked and prevented from blocking all classes etc. In fact if you are claiming lag is that bad, why are you playing, you would get owned by everything all the time.

    Thinking more along the lines of a l2p issue.
    35-40 ms is not lagging that's the best latency I've ever gotten.
    Oh and about the "why not stop playing": Because we paid 60€ for it (70$)? Think about that before non-sense posting. This is a paid title after all and so we should be provided with a more lag-secure system, not the design fail the whole game becomes once you have a latency that's a little worst than the best you could get...

    about l2p: Hammerign dodge before the enemy attack started just to watch your charakter do nothing and get hit with a now undodagble combo, has quite nothing to do with l2p though it's easier to claim everyone just sucks due to it makes you feel superior, but well mate if you need that...


    I main warden and Warlord and they're also getting killed by the conq combo. I don't know how conq players see their champ but in my experience conqs attack pretty fast and they deal about the damage of a warden (I think I remember they were slightly over the warden with some of their heavies).

    Well...so long
    Jack.
    Share this post

  10. #10
    Originally Posted by JackStreicher Go to original post
    35-40 ms is not lagging that's the best latency I've ever gotten.
    Oh and about the "why not stop playing": Because we paid 60€ for it (70$)? Think about that before non-sense posting. This is a paid title after all and so we should be provided with a more lag-secure system, not the design fail the whole game becomes once you have a latency that's a little worst than the best you could get...

    about l2p: Hammerign dodge before the enemy attack started just to watch your charakter do nothing and get hit with a now undodagble combo, has quite nothing to do with l2p though it's easier to claim everyone just sucks due to it makes you feel superior, but well mate if you need that...


    I main warden and Warlord and they're also getting killed by the conq combo. I don't know how conq players see their champ but in my experience conqs attack pretty fast and they deal about the damage of a warden (I think I remember they were slightly over the warden with some of their heavies).

    Well...so long
    Jack.
    You might as well cut losses dude. Ubisoft aren't going to adjust a class to latency, they're not even going to implement dedicated servers. The game will die within the next few months, like all Ubisoft MP titles.

    Everyone lost out on this game, live and learn, dont buy into Ubisoft's BS again.
    Share this post