BlatMan

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.