BlatMan

I've been around since 2011 or so. I've seen it all. I remember the email Gamerfirst sent mentioning APB Reloaded that originally got my interest, after they sold off WarRock. I've seen most versions of Flaw's config. I agree it's cheating, but I also understand why its needed. APB runs like crap by default. That's something Little Orbit kinda fixed with the 64 bit update, but it's still bad, and unacceptable for what little the game is doing. By mouse settings, do you mean the mouse fix that multiplies your mouse input by 2? It's a workaround for APB's broken mouse input. Without going into detail, APB ignores slow mouse movement. This can help mitigate that at really low fps, but for most players it's snake oil. There seems to be a high correlation with cheaters and stretched res, but playing at low resolution isn't cheating. If anything, it's giving yourself a major handicap since it removes some horizontal field of view.

Idk if this is a meme. It's a bug on APB:DB. It's not accounting for the reload time, and it's only counting the first shot's trigger timer. First shot adds the Wind-up Time. Then the next 3 shots use the Fire Interval. Yes, I know multiplication is done first and doesn't need the parentheses. It's for demonstration. Fire Interval: 2 sec Reload Time: 2.25 sec Wind-up Time: 1.75 sec Stock: 1.75 + (3 * 2) = 7.75 CJ3: 1.75 + (3 * 2 * 0.93) = 7.33 But you still might be correct. If the reload time was faster than the firing interval, it might help. I don't know if reloading resets the firing interval, and I don't know if Mag Pull works on the OSMAW currently. I remember them changing MP, and APB:DB shows that the ammo count rounds up. I'm not installing a nonfunctional kernel anti-cheat to test it. Reference from the old DB: https://web.archive.org/web/20190305024734/http://apbdb.com/items/Weapon_Explosive_OSMAW_Slot3/

It wouldn't surprise me. Some days I feel like my account is nerfed. I think it's related to the DDoS protection. I started having these issues when Reloaded implemented the DDoS protection. Hitreg was perfect when it was off, but then someone would DDoS the server, then when the server came back online the hitreg was bad and I would die too fast. Fast forward to Little Orbit owning APB, the same thing happened a few times. I'd notice the hitreg was perfect, and I was living a little too long. Then the server crashed, and the hitreg was bad again.

I bet those cheat points are just the threat system.

Is the ice cream machine still down?

They got fired from Tasty Burger and now work for Micky D's out of spite.

I suspect it's due to the district servers clock compared to your client's time. I noticed a while back that some US servers were on the EU timezone. I'd buy a mod in social, but I couldn't use it when joining an action district. There's no reason to go by the timezone, but this game is built on doing things the wrong way.

I used these a while back to extract from the RTW version and Reloaded's. Watto's Game Extractor. Use the free version. http://www.watto.org/game_extractor.html Umodel. It might not work on the compressed/excrypted files. https://www.gildor.org/en/projects/umodel#files

The first screenshot looks like you smeared vaseline all over the screen. The second screenshot has fog enabled, making it look darker than normal.

Just look at what threads are still pinned in social. It tells you exactly what cultural problems LO have.

The TLDR is, Little Orbit decided to update the existing game's engine to 64 bit instead of upgrading to a later engine. Currently, APB runs as a 64 bit application. You shouldn't get the out of memory errors like you used to with modern GPUs, and your framerate should be a little higher. They have many blog posts about it. This is just the first when they made the 64 bit decision. https://www.gamersfirst.com/apb/news/2022/8/5/message-from-matt

Did they disable the exploding of out of mission vehicles that are parked on mission objectives? Then again, maybe out of mission players should phase through you when you're on foot or at least when interacting with an objective.

It's too good in cqc, but it sucks as a rifle. We have enough good cqc weapons, adding another was pointless. It's the same issue as the Corsair. It's good in cqc, but the damage dropoff makes it useless at midrange. Both weapons look like they should have some range, so when they don't, your brain immediately says it sucks, even if it technically doesn't.

This method no longer works on Linux either since SARD requires the kernel part of the anticheat running.

I haven't been able to reproduce that UI bug, and I'm usually pretty good at finding bugs. Someone in SPCT said it's related to having contacts or other UI stuff enabled. I had a friend use the exact graphics and game options I have set, yet they still experienced the bug. Watch it be related to something stupid, like the character login screen. I use a different login screen to skip the long loading time. Doesn't matter. I still can't launch the game on Linux, nor can anyone who uses the Steam deck. Well, technically it's possible, but I rather not attempt to bypass an anti-cheat that's so unpredictable that it even kicks legit Bronze players.

No shit. They purposely put that message to be vague. They could have shown the generic ban code, or even better, not banned the account at all and instead generate a customer support ticket to look at it. I thought that's what they were going to do since they seem iffy about banning players to begin with. Come on LO, at least be consistent. Then again, I guess random is technically consistent if the result is always random.

In the past, my game crashed if I switched districts too many times, even after the 64bit update. I wonder if the servers have the same issue with players constantly switching districts due to the cross-district matchmaking.

The range wasn't the problem with the Scout. The problem was you can hit players while jumping behind walls. Besides, the reason the Scout's jump shot was nerfed is because Reloaded wanted to milk the whales. They released the Dogear in the same patch, which has the ability to jump shoot.

"If we have 100% confidence that you are cheating, then you can be banned at our discretion. We have found that there are some players who cheat at a level there is no other solution. We have to ban them. It's unfortunate, but we can't ignore it. Cheat at your own risk. You may lose your account." In other words, you will ignore players who are 100% cheating. If you were really going to put in any effect, you will have said "will" instead of "can" and "may"

Does your mouse have custom profiles per game? Maybe that's interfering. I can't think of anything else.

Green? Do they play 1 mission, then go afk for the next 100? Seriously, green is much harder to hold than bronze if they're actually participating in the missions.

What broke this time? I'm just curious.

True. EAC wasn't any better and they allowed it. Then again, there's like what, 4 people including myself? I don't spend money on the game, and probably won't with current management.

Idk how SARD can support Linux without opening security holes. The best thing to have is server sided detection, but I doubt LO will ever get that working. Remember phasing for matchmaking? That never happened.

I've been here since 2012 or maybe even 2011. The majority of dethreaters were silver threat, but they got gold because they didn't have better players to fight in the lower threat districts. The people complaining about them are people who expect the game to play itself.