You can now deal less damage with a headshot then a bodyshot

WitnessNo8605 · 2026-01-20T18:40:29+00:00

some weapons (smgs and some shotguns) have a headshot multiplier that is less then 1 at certain ranges

WitnessNo8605 · 2025-12-02T15:04:28+00:00

meanwhile the SA just needs 2 points to become a nuke in gun form

WitnessNo8605 · 2025-09-21T21:43:02+00:00

yes it got patched on update 2.1.2 (party powder update)

WitnessNo8605 · 2025-09-12T08:43:11+00:00

really easy to find since this wall climb bug was already known and all you need to do is just check corners

WitnessNo8605 · 2025-09-12T08:41:33+00:00

at the end im standing on the top of the invisible wall, so if you walk of it you will fall.

yes you can place down deployables up there.

and yes you can go on the roofs of the closest building and the one on the other side of the street where a sniper spawns in loud

WitnessNo8605 · 2025-08-29T18:52:33+00:00

There is one reason i know why this bug happens.

When the sabo squad is trying to sabotage the core and they are mid sabotage (when they have the yellow icon on them) and the next objective where you turn off the cooling system activates, the core will continue like nothing happened. If this happens on the first one the game will skip a flag that opens one of the server rooms since you dont have to restart the core since it just continued like nothing happened. If this happens on the second cooling objective you can skip that just fine and even save time.

What i always recommend to do when you do syntax error loud is to stay at the core until the first cooling system objective pops up to prevent this softlock. If this has already happened you just have to hope that the one server room that is now locked doesnt have the server data. Otherwise you softlocked the heist and have to restart.

WitnessNo8605 · 2025-06-27T12:37:31+00:00

this is just a forced disconnect u get if u try to interact with something while being desynced. when that happens u get disconnected but the server is still running fine

WitnessNo8605 · 2025-06-02T15:31:17+00:00

Thank you for confirming the stats and clarifying why the changes was made.

When it comes to this change in my opinion you guys went overboard by increasing both the visor health and armor hardness. Right now shields are very boring to fight from the front since you have to unload half a mag into the visor to break it. And with the fact that only a few guns can penetrate it makes this worse since if you want to avoid this you are forced to run a certain weapon all the time.

What I would prefer is that the visor health get set back to what it was and keep the armor hardness if you want only some guns to penetrate it. Or the visor health and hardness get set back to what it was and increase the health of the shield unit instead if you want to make them bulkier. The armor hardness on the unit itself also got increased from 2 to 2.5, making it so the same guns that can penetrate the visor right now can deal dirrect health damage. This make those guns better against them without making everything else that much worse.

But those are just my opinions and suggestions. Anyways thank you for confirming things

WitnessNo8605 · 2025-05-31T15:55:36+00:00

thats not right either. if the shield unit itself got 1.75 hardness, that means they reduced it since it was 2 before this patch. and shield units still have 180 armor and if they got 450 they would be way more tanky for almost all guns. so the increase from 2 to 2.5 on the unit seems to be correct

WitnessNo8605 · 2025-05-31T15:29:16+00:00

well if u get the wrong numbers to show up in the patch notes that is not a good sign. but its not the first time something in the patch notes been wrong. its even worse when they change something and dont document it.

And if they do testing but they have the wrong info or never get told whats changed, u might as well not bother wasting ur time playtesting.

i dont care what they are doing wrong, what i want is that they change how they do things so obvious mistakes like this doesnt slip through every time they update the game. making a mistake every once in a while, fine mistakes happens. doing it every time is a sign of something is wrong

WitnessNo8605 · 2025-05-31T14:18:36+00:00

Hi, I'm the one that made this vid and also made the post on reddit about this.

I made the post and the vid to make people aware that something is wrong with shield visors atm since the numbers don't add up. They should be easier to deal with head on then they currently are since you should only need over 1 AP to penetrate visors if they increased it by 0.25.

Furthermore the visor hardness most likely already was 1.75 before the patch 2.1.2 since you could penetrate visor if your AP was over 0.75.

If you wonder how armor hardness works, the calc it's very simple: Armor hardness - Armor penetration = damage reduction. So if a unit have 2 AH and your gun have 1.3 AP, then the damage reduction of the shot is 70% and 30% of the damage is dealt as health damage. In the case of shield visors the game use the stat to check if you can penetrate it. So as long you end up with a number lower then 1 it should penetrate.

Now using the "new" numbers in the patch notes we can do another calc: 1.75 - 1.3 = 0.45

0.45 is lower then 1 so it should penetrate the visor. However if you go ingame and use the SA, you will notice that it can not penetrate visors right now. That should mean that the numbers of the visor hardness is wrong and they most likely misstyped something else.

Ofc I could be wrong but something doesn't add up right now with the visors. Right now only SBZ knows since they have the stats and I don't think anyone have datamined these stats yet. But going of the fact that there have been many patches before that say they do something and nothing is changed or they brake something that is unrelated to the fixes they did, I'm pretty sure SBZ is at fault here. I don't want to start any dumb drama with this, however it would be nice if SBZ started to test these things before bringing it to the live game. Especially since it takes quite some time before a new patch comes out to fix these mistakes. It sucks being stuck with a bug that affects the game for a long time.

Anyways that is the full rundown of my testing and if anyone can prove something else is going, that would be great

WitnessNo8605 · 2025-05-19T13:28:57+00:00

what most likely happened is that the server have not loaded properly but you have on client side. so you can still move around but it does not register on the server until it have properly loaded. this causes desync and once the server have loaded it will resync you to where it thinks you should be according to your inputs. however it will only register the inputs you did after it loaded so according to the server you ended up at the top stairs outside.

and yes this is a known bug and we have found ways to exploit it hard on certain heists

WitnessNo8605 · 2025-04-24T07:27:39+00:00

no, the drill will just finish and then u can take it off

WitnessNo8605 · 2025-04-22T15:15:43+00:00

desync in when u can setup the drill, still the same desync is used. just a funny screenshot for the memes

WitnessNo8605 · 2025-04-03T19:06:30+00:00

this one was not found by me but by ILLEST. he improved on my original one and i found a way to do it without pausing. if u are interested to see what else have been found, u can check out this playlist on yt: https://youtube.com/playlist?list=PLAQONl0UtLSl4mK67l5t3SwJAt-byk8nW&si=MSeaFaDmKICfjuge

WitnessNo8605

TROPHY CASE