BleepingComputer.com: Game 'Anti-Hack' programming

I've been asked too program a 'Anti-Hack' for a private server me and a couple of buddies are running. I would be all for this but I figured with my programming knowledge being limited too VB.NET I figured I had some research too do so I have a few questions:

First off, what language would this be the most efficient too be programmed it?

The main focus of this 'Anti-Hack' at this time is too be blocking macros. How would I go about blocking specific Macro-ing programs or keyboards with out blocking their specific keys off of the keyboard

Any thoughts? Thanks for the help!

What do you know about handling OS calls? What do you know about heuristics? How do you programatically determine if someone is running a macro?

Quote

Programming knowledge is not limited to any language. Your programming vocabulary may be limited to VB.NET, but a for-loop works the same in any language. If you can do it in VB.NET, then with a bit of research, you can figure out the syntax to do it in Java, C#, or any other language.

I know nothing about those. Would that be what I would have to begin research on for this project?

Learn about operating systems, starting with something like Minix. Learn how the system calls work together, and how they can be altered to suit your purpose. Then probably check out some Windows APIs and learn how to use them. Doing what you want to do requires some in depth understanding of how operating systems work. In 6 months or so, you should have a good idea of where to begin.

I still have no clue how you would differentiate between a macro that is manipulating a game, and any other application on the system. About the only thing you can do is check and make sure that game values are within acceptable parameters.

I will definitly begin too research Minix and how it works. You woulden't happen too have a guide poking around some where on how too get started in understanding these system calls? What any of the mean?

groovicus, on Jan 4 2010, 01:50 PM, said:

I'm not too sure about this, but I believe that you'll have to poll the keyboard drivers (maybe on an assembly level?), to make sure that it was the keyboard that issued a keystroke, rather than a macro inputting text into your program's GUI.