Preventing CheatEngine

well in this stage i work on Disabling Bots / Macros and hacks .. atm i successded in Disabling using Speed Hack And Reviver Hack too .. but i'd like to know how to Disable using CheatEngine cuz by it they can change Item IDs or w.e they do ..i used method to kill proccess of CheatEngine but it doesnt seem to work except on my Maching ..so i need to know if there are ways to Prevent using this Shit Prog in my server

Regards
shadowman123

If you're allowing your server to be exploited by someone changing an item ID, I think you should fix it in your server rather than struggling with a workaround.

On-topic, no, there's no way to stop CE permanently.

As mentioned, server side security is always the best first step. You need to ensure you're fully checking every bit of information the client is sending you or there will always be ways to exploit your server.

Killing processes by ID/name/etc is... not ideal because people can just create their own slightly altered program (I know it's pretty easy to make a 'custom' cheat engine client). Better off checking everything server side and then some basic changes to the client to stop 99 pct of normal botters (changing enc key, overwriting some basic packets, etc)

i do know that the server side work is the best Solution ... but idk y they change the ItemID .. if i knew that i'll be able to fix the solution but actually idk

Quote:

Originally Posted by shadowman123 i do know that the server side work is the best Solution ... but idk y they change the ItemID .. if i knew that i'll be able to fix the solution but actually idk

You should probably focus your efforts on fixing that problem then, not on implementing an anti-cheat engine that will never be able to fully protect the server from members who decide to take advantage of your exploits.

after a while of searching i found that they use the cheat Engine to change Item Id to be able to open socket in it .. its too easy to fix now Thx Alot every1

Quote:

Originally Posted by shadowman123 after a while of searching i found that they use the cheat Engine to change Item Id to be able to open socket in it .. its too easy to fix now Thx Alot every1

i've gone way too far with this
and as everyone else said , server side checks should prevent anyone from doing such stuff
i've written a thread about exploits before , find it in my sig.
i've given examples for it includes but not limited to changing items id's to bypass client side checks
but to sum it up
add check on the item usage section on trinity at the socketting section to see if the item is valid to add a soc in it
also you can go a bit more wild with it using a simple method to do more checks on the item while upgrading q or l and socket
there is some bug in trinity for upgrading the level of level 1 weapons which turn to be refined/unique level 127 wep which people may abuse
all of that could be solved with a hard coded method to check for everything
should looks like
bool itemusagemultichecks (enum wayofupgreation , item item)
switch
case socketing
check on item id , level , chances , pla pla
if cheating then ban
return bool

well i've fixed this issue 2 Hours Ago Thx dude .. u alawys Help others and thats smthing i Respect anf Appreciate

The problem probably lies in that you do not verify the UID's that comes with the packets.

Quote:

Originally Posted by shadowman123 well i've fixed this issue 2 Hours Ago Thx dude .. u alawys Help others and thats smthing i Respect anf Appreciate

at some point everyone needs help , no one is omniscient , which to why we are all here
however the most successful people is who can resist asking whenever they found something they don't know and spend hrs trying on there own (which actually require alot of time which many of us don't have)
but still one rule applies all the way throw "people don't want to see you stupid but also they still don't want to see you better than them "

Quote:

Originally Posted by Super Aids The problem probably lies in that you do not verify the UID's that comes with the packets.

exactly , you get the item uid / id , update the item but never check for anything (which makes logic , no one was to expect checking for such a thing cuz of the client side check before someone actually exploit the hell out of it)