Basicly, I've been working on preventing these from viewing the memory/editing the memory on the fly in my game, for example.
And yes, I do understand the difficulty or doing this, and yes, it is a client/server, and I do understand the only real solution is to add checks to the server side too. Right now unfortunatly, theres more work then needed, for example, the server/client lag coding needs alot of work, thus it can get laggy at times if you send too much stuff at once. More or less this would cause an issue, and the game is more based on how CS or Continuum is, like stated before.
However, jkr did point out some interesting things, at http://www.codeproject.com/KB/security/AntiReverseEngineering.aspx?fid=1529949&fr=51&df=90&mpp=25&noise=3&sort=Position&view=Quick#BpMem
... Which prevents some things. Currently I do have most debuggers stopped using some coding w/ page guards..
However, I believe basic memory editors (not debuggers) are still going through using 'ReadProcessMemory()' and 'WriteProcessMemory()' .. It uses a different way to 'attach to the process' is what I am guessing. More or less I just want to hinder them from writing in the end, but if it can hinder reading or attaching too, that would be great.
Using Page Guard for example, I haven't been able to find a proper solution, and I am not sure how to 'prevent' memory editing from occuring.
I am not trying to make it 100% proof, more or less I know that is impossible. I wish to however, hinder the basic 'cheater' as this would proabbly hinder at least 90% of people. Most likely.
Could I get more assistance on this? I apologize for the second question, but I am myself learning C++, as I have just gotten into it a couple months ago.