Frosi

The creator of APBDB was recently provided with the most up to date stats which means that the most recent update should show all changes that happened in the last couple of weeks which means that all of these changes are already in the game.

Previously the Corsair had 30 meters of effective range and a 5 meter minimum damage range which meant that at 30 meters and onwards the damage would nosedive to its minimum percentage damage of 45% of the base damage after just 5 meters. Here's an example: Prior to this patch the Corsair would deal 400 Damage within 30 meters and afterwards have that damage drop to 180 (45% of its base damage) over the course of 5 meters. After this patch the Corsair will deal 400 damage within 30 meters and afterwards have that damage drop to 120 (30% of its base damage) over the course of 25 meters. This means that because the damage doesn't drop as fast as its drop is now stretched out across 25 meters rather than 5 meters it will now be able to 3 shot up to 35~ meters, however, this comes at the cost of no longer being able to get a 6 shot kill at up to 100 meters as I felt that this was a bit excessive given the rate of fire buff. Do however note that all of these changes are subject to change in future passes, generally speaking the goal is to ship changes that work mechanically and then improve upon them in further iterations if required.

Yes it will apply to all version's of the Cisco whether they come from a contact or other players. Essentially when accelerating (Holding W) the car's chassis will move based on how much Torque the vehicle has, to make sure that the car doesn't do a straight up wheelie the ChassisTorqueFactor modifier exists which decreases how much the chassis moves. The Cisco used to be set to 0.015 but was accidentally changed to 0.04 sometime around christmas last year which created a scenario in which the wheels would clip through the chassis quite frequently. This change aims to fix the clipping issue and has no real other effects on how the vehicle handles so don't expect it to handle any different than you're used to.

Oh yea lets nerf a weapon because cheaters use it thats definitely how game balance works

The new Engine got cancelled because porting it to 3.5 was just a flawed concept and LO realized that its not going to work way too late. APB runs off of a ton of custom code which was not part of the 3.5 Engine upgrade which has lead to many issues and horrible performance. Instead they ported the game from 32Bit to 64Bit which essentially achieves the same thing in the back end which is to allow for major improvements and more modern solutions to be used in the game but visually to us the game looks the same so it is less fancy than upgrading to a newer version of the Engine.

No it does not, the title means I test patches for LO or give feedback on things they are planning to do. This is a voluntary role and involves no payment whatsoever. I'm not even gonna go into the other ramblings you decided to post because it turns out, it wasn't EAC as expected and was an issue on Respawn/Apex's end that they have started to patch, on top of that, looks like the two players that had cheats injected into their game were injected by a Trojan or other bits of malware prior, possibly through said issue on Respawn/Apex's end.

There's a few reasons why I believe its not related to EAC, primarily the fact that its isolated to Apex which runs on the source engine and Source/Source2 has had a few similar RCE exploits such as the ones seen in this clip. Also, for now the issue seems to be isolated to Apex, its yet to pop up in other games which it would've by now if the issue was related to EAC. Sorry for not being a cry baby that posts delusional takes and miss information on the forums all day, I know I'm the odd one out. If there's a vulnerability what do you expect LO to say/do about it when EAC themselves says they are confident there isn't one? The forum (as usual) is fishing for answers/clarification for things that LO themselves can't comment on or potentially aren't even in the know about because EAC doesn't have to tell companies that use their AC anything, pointing out said things by using common sense apparently means I'm paid to defend LO.

People are jumping the gun about a RC Cheat injection being related to an anti-cheat but it has happened in other source games before. I'm sure EAC doesn't care about what some people on twitter with zero knowledge about anything anti-cheat let alone RC injection related are talking about. So far, the RC injection seen recently during an Apex tourney has only affected Apex legends, if it was a serious issue it would've affected other titles by now.

Twitter comments are about as high value as 90% of posts on this forum so they are nothing to pay attention to.

Probably trust the official stance of Epic? Seems like whatever happened at the Apex tourney was unrelated to EAC and potentially related to Apex/Respawn/EA services themselves. This would also make sense because of quite frankly absurd cases of exploits / potentially cheats happening in Apex lately such as an entire lobby being flooded with AI Controlled bots that hunt down and only target certain streamers.

Trade locks are caused when you log in from a new IP, after a windows update or when you changed out parts in your PC since the last time you logged in. This usually only lasts for 3 days and aims to protect you from any sort of account theft.

That would do absolutely nothing because that'll be a 0,2 second lockout that prevents you from switching which will do nothing but feel clunky rather than serve as a "nerf" to the gun.

Its almost like these are test listings

Literally posted minutes before the shut down, whilst the countdown for the shutdown was rolling but its okay, I know you like to complain for the sake of it

Crazy, guess I must be hallucinating about the literal announcement made on discord before the servers were being restarted.