🛈 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. #21
    FledgeSRondo's Avatar Member
    Join Date
    Mar 2017
    Location
    Ashfeld
    Posts
    113
    Wow, that is just... that is absolutely ridiculous. That needs to be fixed ASAP.
    Share this post

  2. #22
    the best way to fix it is have a zone where the players spawn that the enemy cannot enter.

    but knowing ubisoft all they gonna do is probably just put some boards with collision so players don't fall off the back but that means you will still get cutup when spawning
    Share this post

  3. #23
    Easy fix. Just put a barrier behind any spawn points so they can't ledge you. Done.
     1 people found this helpful
    Share this post

  4. #24
    Originally Posted by RROARGATHORR Go to original post
    Easy fix. Just put a barrier behind any spawn points so they can't ledge you. Done.
    True thats what i said also but if the whole team was there they could cut you up really good before you can even move so still be dead
    Share this post

  5. #25
    OMG i didn't know. Can't wait to try this 1!!
    Share this post

  6. #26
    Originally Posted by RROARGATHORR Go to original post
    Easy fix. Just put a barrier behind any spawn points so they can't ledge you. Done.
    Pretty much this ^^^^
    Share this post

  7. #27
    TwinStiletto's Avatar Member
    Join Date
    Sep 2016
    Location
    Texas
    Posts
    83
    Report the player. The devs need to see what a cheap tactic this player was using.
    Spawn killing is a very low form of play.
    Share this post

  8. #28
    Originally Posted by TwinStiletto Go to original post
    Report the player. The devs need to see what a cheap tactic this player was using.
    Spawn killing is a very low form of play.
    Spawn killing is the second lowest form of play.


    The only thing worse is outright exploitation and/or hacking.
    Share this post

  9. #29
     1 people found this helpful
    Share this post

  10. #30
    No response from anyone
    Share this post