Quote:
Originally Posted by -Mac-
Or if you wanna do it in a classy way, make a dll that would stop the client being launched with Cheat Engine.exe; or if it is ran while the client is running, then the client should close.
I don't know if it's possible, but yeah why not.
Either way, I think you should do what p4n said, then do the dll as a just-in-case resort.
|
You could easily write a loader that runs in the background during the client and does all sorts of cool security measures like for example...
-Changing Client Encryption
Would completely remove any proxies/most bots from working on your server
-Changing Spell Encryption
Would fix 99.99 pct of aimbots
-Scanning the running programs
-Scanning the client itself
-Sending verification information to login server to not even allow a login attempt if any checks fail
You could do more then that but those are just some things that pop into my mind that you could do through hooking various client methods and editing the conquer.exe but that's above almost everyone on epvp (myself included for some of them).
Server side protection is ALWAYS highest priority and simplest to do though cause ANY and ALL client protection CAN be cracked.
If you check everything server side then no possible client side hacks will work (yes, proxies/bots will still gain advantages... but far less then they would otherwise)