The Finals Aim Assist Nerf Is Having New Problems

Everyone is here, and it should come as no surprise that the developers at Embark Studios have taken a pretty aggressive stance when it has come to assist and console players. But without further ado, let's jump into today's topic. As most of you are probably aware, unless you've been living under a rock, the finals have recently undergone a pretty significant change with the release of patch 1.5.

I mean, we're seeing Buffs and Nerfs all over the place, and while the developers did initially address concerns around aim assist in the prior patch 1.4, the latest update has introduced even more new issues, including the inability to avoid crossplay aiming sensitivity, resets on cons, and the addition of scope sensitivity, so let's go ahead and actually start off with the whole aim assist debate and the developer in Bark Studios's justification on why they did it, you see.

Dusty Gustaf, who was actually a customer support lead at Embark, went ahead and let us know the rationale behind why they made the alterations. Apparently, they analyzed data comparing mouse and keyboard users with controller players and determined that an assist provided an advantage to the ladder.

I mean, that's not very surprising, but they didn't go much more in depth. He did, however, emphasize that decisions were based on internal data rather than the volume of player voices, which is interesting to see because there are a lot of player voices. I do think that something in the future they should do in the future is let the users see that internal data.

It's very easy to say we have a ton of data but then not actually show any of it, which doesn't mean much to the players in general. However, the changes overall were welcomed by players, with one Reddit user actually expressing gratitude for the Embark decision and transparency. I will once again say they are very on top of these updates and changes.

However, with the assistance of Nerf, there were some unintended consequences of their latest 1.5. patch because now there seems to be an inability to enter lobbies with crossplay turned off. I see there are some users on Reddit saying that despite selecting this option, they're finding themselves in crossplay-enabled lobbies, eliminating the ability to avoid PC players, which is a huge issue when you have no aim assist or it's been turned down quite a bit.

It's one thing to play in a console lobby at 60 frames per second lock against other players in the same predicament with equal assist values, but now you have to go up against people with better hardware, possibly getting their entire arm to aim and shoot you. I'm not saying AIST is now underpowered or overpowered in the past; I'm not saying that mouse and keyboard players have a clear-cut Advantage: What I'm saying is that if you have a crossplay function, you need to make sure that it's able to be turned off if you have lowered the assist values.

That's just fairness, or at least allowing players to have preference. Along with that, there was another thing that was actually reset. According to some Reddit users, that's the aiming sensitivity if you are on console, particularly. This seems to be impacting the PS5. I'm on Xbox; sometimes when I play.

I haven't noticed it, but one of my teammates, who was actually on PS5 when we were doing rank, did notice this as well, and there's a new scope sensitivity that seems to have inadvertently reset the normal aiming sensitivity, and that has left players feeling disoriented. As the familiar sensitivity settings they had adjusted to were unexpectedly altered, now that you're forced into crossplay lobbies, your aim assist is lower.

People are basically getting lit up in these PC lobbies, and unfortunately, Embark has not addressed the issue or made a statement to let players know that this may be impacting them. The lack of prior communication about this reset has actually fueled quite a bit of dissatisfaction amongst the player community.

Luckily, there are YouTube channels like this one that kind of cover this stuff. Watch what's going on to kind of inform as many people as they possibly can, but if you're playing on console and if you've noticed some major changes, you're going to want to go into your settings and start making adjustments, trying to make sure that crossplay is turned off even if it may not work.

There's a ton of Reddit threads that have been cited; you can see them up on screen, and there are some users expressing their frustrations. With the crossplay issue with one St after the new patch can't get into lobbies with crossplay off the sentiment and thread reflects a lot of discontent, because well.

I do think that this game is moving towards a mouse and keyboard slpc. User base: it is still important for the game's longevity to also look at the casual player base that plays on console and make sure that they are also able to play the game and enjoy their time and experience. On it. I will say they did something pretty interesting for console players where they were actually disabled: a mouse and keyboard that were able to be used on the console through third-party software.

Some people are very upset about this article shed, and some people are very upset about it, but hopefully with all these things going on. Embark Studios is fully aware of maybe this article shed some light and makes them aware as well. They are pretty active, so I hope we see a lot of these fixes come out very soon, as right now I can actually see a ton of discontent in the console community about just how the game isn't exactly favoring them or that it feels like Embark Studios is ignoring them.

Also, don't forget to check out this channel right here by my edit Noel, who does amazing gameplay and content on the finals. Until next time, everyone.