It happened to me several times but i was never able to record it ! Sometimes when i used to login i would spawn without any weapon when i would be 100% sure i owned several weapons before quitting! Not sure what is the reasons! But recording this is quite impossible and hard as it happens as soon as you log in!
Weapons are remove after log in
Locked
Bahzi wrote:
Which weapons were gone. The weapons you bought as police officer or those you previously owned as a civilian?
Both in civilian and also cop. it's randomly gone like one time sawn off gone and another one time deagle gone while this are in cops. while in civilian one time chainsaw gone. But this is happening when i quit the game for hours then login in game.
Parzival wrote:
speaking as I experienced this more than thrice, this occurs due to high packets loss, the weapon ammo count messes up and the server just decides to take it all away because it's unable to correct it-
May be, i'll check it next time, if i got packloss.
This has happend to Stalenin today when the server crashed,
Basically the players don't lose the weapons, they just have them in their inventory with 0 ammo.
I think this occurs when you are having bad packet loss or crash, then rejoin. Maybe the anti cheat might remove them? Or maybe it's just a script error that occur?
I will be investigating each time this happens with a player and will send any more details I find about this matter here..
Basically the players don't lose the weapons, they just have them in their inventory with 0 ammo.
I think this occurs when you are having bad packet loss or crash, then rejoin. Maybe the anti cheat might remove them? Or maybe it's just a script error that occur?
I will be investigating each time this happens with a player and will send any more details I find about this matter here..
The weapon anticheat works as follows:
The server knows what weapons you should have, and what ammo you should have for them:
- If your game tells the server you have more ammo than you should, it will remove the excess ammo.
- If your game tells the server you have less ammo than you should have, the server updates its knowledge of what ammo you should have by reducing it.
- If your game tells the server you have a weapon that you shouldn't have, it removes it.
- If your game tells the server you no longer have a weapon you had, the server updates its knowledge and removes that weapon from its memory.
- If your game tells the server you have 0 ammo, it doesn't remove the weapon, nor does your game, it's still in your inventory and the server's memory as having 0 ammo, you cannot select it in your weapon selection thing.
So if your game tells the server you now have 0 ammo, the server trusts you and updates its internal memory. I don't know why the server and/or player crashing/timing out would do that. I don't think it would, or we would see this issue much more often.
Then, we have to factor in the civ/cop loadout system. That seems to be where this issue in particular is. If we can do some testing and working out why that is, that'd be useful.
Can we 1000% confirm that it's simply the ammo gets set to 0 and the weapon stays? Can we try DIFFERENT weapons in civ/cop loadout so it's not confusing? For example try with a sawn-off shotgun in civ loadout but a combat shotgun as a cop, so we know what is being affected by what.
The server knows what weapons you should have, and what ammo you should have for them:
- If your game tells the server you have more ammo than you should, it will remove the excess ammo.
- If your game tells the server you have less ammo than you should have, the server updates its knowledge of what ammo you should have by reducing it.
- If your game tells the server you have a weapon that you shouldn't have, it removes it.
- If your game tells the server you no longer have a weapon you had, the server updates its knowledge and removes that weapon from its memory.
- If your game tells the server you have 0 ammo, it doesn't remove the weapon, nor does your game, it's still in your inventory and the server's memory as having 0 ammo, you cannot select it in your weapon selection thing.
So if your game tells the server you now have 0 ammo, the server trusts you and updates its internal memory. I don't know why the server and/or player crashing/timing out would do that. I don't think it would, or we would see this issue much more often.
Then, we have to factor in the civ/cop loadout system. That seems to be where this issue in particular is. If we can do some testing and working out why that is, that'd be useful.
Can we 1000% confirm that it's simply the ammo gets set to 0 and the weapon stays? Can we try DIFFERENT weapons in civ/cop loadout so it's not confusing? For example try with a sawn-off shotgun in civ loadout but a combat shotgun as a cop, so we know what is being affected by what.
Now a days can't find this bug. Like mike said, weapon anti-cheat scripts. if someone have high packloss only, the weapon anti-cheat detect that player and remove some ammo/gun randomly. So pls lock this topic.