Detect Desync

[Donnovan]

There is any function that returns the player Desync?

 

My idea is to avoid player to access gear when he is under desync.

 

Thankyou!

[raymix]

Don't think you can, unless you make do PVS and expect answer in timed manner, still not reliable solution.

Is this for antidupe? 

[Donnovan]

Yes, this is for a anti dupe.

 

Its really simple. If the player is under desync, he cant access the gear.

 

I liked your solution, may be send a boolean every 1 second to each player is not that expensive.

[raymix]

desync is a "naturally" occurring thing, too, sometimes it can last quite a few seconds. Sending PVS from all clients that often is quite expensive actually.

Is this the issue with players disconnecting cable and returning to lobby dupe?

If so, keep in mind there are several namespaces you could utilize to help you on your quest. missionNamespace used by default is cleared when in lobby, uiNamespace and parsingNamepsace will persist until game is closed.

 

Also this should force them to restart the game manually if you are 100% duping is happening, thus not saving their duped items, but be careful - as I said, desync works in mysterious ways

[Guest]

Right if you really want a AntiDupe, create a .dll and save players gear in a private File, which you can encrypt with a md5 hash + player uid as key.

[Donnovan]

Thanks for the help.

 

The kind of dupe happens when the server is under desync, and is done exchanging gear with a vehicle, with driver ejecting and players ejecting. This desync problem can happens because of server connection problems, but if there is no desync a group of player can generate it like then all seting view distance to 5000 using our avaliable server options.

 

Another way is this group doing multiple suicides, causing execive dead bodies and generating lag.

[Brian Soanes]

You can't detect desync as it's handled client/client/server, the same as bandwidth monitoring, it's unique to that client.

Plus, if the server is desyncing running things to detect stuff in that state is a big no no, the best course of action is prevent it from desyncing. 
Lower vehicle count, lower player count, optimise networking and Arma networking, streamline extra scripts so they're not pv'ing everyones inside trouser leg and saturating the server.

 

 

 

a group of player can generate it like then all seting view distance to 5000 using our avaliable server options.

 

There's a clue there, you're giving your players a tool to cause desync!

[Donnovan]

Nice, but players will try to do that when they see the red chain, or when their desync on "p" is 100000. So know if the red chain is in the screen or if the desync value in "p" is 100000, two things that are in the client, already serve the purpose.

 

The maximum view distance is 2500 now. We never had suicide, and will continue without it.