At the moment, the only thing you can really do is make it more tedious to save a full map by only replicating part of it to a client at any time, so the exploiter would have to save each part individually then merge them, which would waste their time.
This. Agreed. If we were dealing with code, the strategy would be obfuscation, which is not perfect, but the idea here is to increase the workload of someone who is trying to cut corners on time.
I think for securing models the only available strategy is to fragment the asset such that you have a bunch of parts, and then assemble the final asset at runtime. Not sure this would be worth doing unless you have something really amazing. I think unless they can steal server scripts, a thief really just has a bunch of parts and no game.
The entire script becomes useless if a player joins the game then uses their own exploits to kick them out. Leaving them with your entire game as you can still download games even if you’re kicked
Your logic on this is terrible, and how many times do I need to explain that even once kicked, you remain in the game’s memory and your client is still being fed the network data, which means ALL scripts still work, because they are ALL executed in that memory. Therefore, even if you kick yourself to try and avoid detection, you would still be detected, and also crashed.
Get your “facts” straight , I never mentioned you “should” use memory checks to detect saveinstance, all I did was give an example of finding unintended side effects.
Yes cut the part of the beginning of my example and leave the following idea of assumption on top of like a leech, you might be the guy to wrongly check for memory leaks, cause I even said that some saveinstances might cause freezes. You also sound like you would flag your players on first leak .
Wouldn’t be even surprised if your game is coded so horribly it lives on memory leaks.
Oh yeah I’m 100% percent serious, Valve Anti Cheat is so good, in Counter-Strike 2, you can’t tell the difference between a cheater and a really good player
“For example most saveinstances freeze for a second causing your client to have memory leak for a second, so on client just detect those leaks and freely assume your game is being saveinstanced (assuming ur game is optimized and doesn’t have own spikes)”
Always was? You have some serious reading comprehension issues.
If you do it incorrectly, any detection can be false positive, you don’t flag person once to instantly assume they are cheating / exploiting.
I’m passing the same question I asked the mr.ai_mzz genius to you, since he was silent on that.
Do you ban your players instantly after they get their mouse on enemies head for “aimbot”?