Skip Navigation
68 comments
  • As someone who has played competitive FPS games at a highish level in multiple games for most of his life I cannot fathom why they ever combined the two in the first place. Like I obviously understand more players and quicker matchmaking, but at the cost of competitive fairness??? No thanks.

    Controllers playing against PC is fine without any any aim assist as that is just straight up a disadvantage for the controller player 99.9999% of the time, but the moment they add any aim assist to the controller it kills competitive integrity.

    Controller players should only ever go up against other controller players if any amount of aim assistance is turned on and same goes for mouse and keyboard. That shit should not be on consoles and allowed to play against controllers for any reason.

    I pretty much dropped Apex Legends entirely just because I wasn't having fun anymore. I was a diamond player on M+KB and getting laserbeamed from across the map by a controller player just was not fun. Just like I am sure they hated getting hit by a nasty flick only possible with a mouse.

    Player input uniformity is one of my biggest gaming gear grinding situations. It's especially problematic with my favorite genre of games: competitive FPS games.

    • It depends on the game, really. Some games balance controller and M/K inputs very well, and I appreciate cross-play in those games. In my experience, Apex is particularly bad about their input balancing and gives way too much advantage to controller users, which is why XIM/Cronus cheating is so prevalent.

      But, you can definitely still have a competitive and fair balance between inputs. Destiny 2 was actually really good about this, and their weapons team did a LOT of work to make sure that matches between console and PC players felt good even at high levels of play, and they nailed it, imo. I think part of the way Bungie made it work was by making every weapon have intrinsic aim assist, even on M/K. This allowed them to tweak that value for each input mode, so that guns felt right regardless of what you played with.

      And the tradeoff wasn't just "extra bullet magnetism in exchange for slower aim speed", they also increased the visual recoil and screen shake effects for controller users, so that the aim assist wasn't completely free, all on a per-weapon basis. Despite Bungie's flaws and numerous missteps with Destiny, this is something that I don't think they get nearly enough credit for.

      • I don't want to seem dismissive, but I have had this argument 100s of times with an untold number of people over the years. If you ask any pro FPS player who has played at a top level on both they will all tell you that the two should never cross. At least not in any competitive/ranked situations.

        It does not matter what you do. If there is anything altering the players inputs whatsoever those players need to be playing against only other people with those same assists and controls.

    • I mean who really cares for pub matches? If you are worried about competitiveness then play pugs. Team stacking and pub stomping isn’t competitive

    • but at the cost of competitive fairness??? No thanks.

      You do realize current CoD is matchmaking based on engagement, right?

      If it takes 3 matches of getting stomped to exit the game, it'll give you an easy win every 3 games.

      If the first number changes, so does the second.

      That's not even getting into how buying skins artificially reduces the second number.

      Like, after accounting for just those two things, it's kind of absurd to complain about fairness unless it's competitive mode, and I'm pretty sure those already have pc/console splits.

      Player input uniformity is one of my biggest gaming gear grinding situations. It’s especially problematic with my favorite genre of games: competitive FPS games.

      That's how it was split....

      A PC controller would be matched up like a console controller. Now pc controllers will be grouped with PC mouse players....

      You typed a lot but don't seem to know what you're talking about about bud

68 comments