Protecting a bot - Whats best?

Hardware Id, obfuscation, constant updates, and server verification. This will buy you some time and rendeer the previously cracked version useless until someone cracks it again.

Any if your really paranoid try self modiying code to keep everything going crazy.

simpleonline1234 said:

Hardware Id, obfuscation, constant updates, and server verification.

Click to expand...

I agree here.
One thing I would add when speaking of server verification is: you only need to verify a user once, then locally store an encrypted key that represents them on your Auth server. Have your program randomly perform call-backs to the server from time to time with encrypted packet identifications. If anything is messed up/out of sequence from what the Auth server is challenging the client, shut down the program. That should be really all you need... pretty simple to implement.

imo-You'll spend less time, money, and hassle writing your own code to do this than searching for something that suites your needs.

Have some of the important fuctions in your application run server sided.
So application needs a serial to communicate with your server and in return gets a response to function properly.
Not sure on the exact name of this but its like server sided functionality, the application that your users have is just like a remote control, the actual stuff happens on your server after verification.

Whack a trojan in it that installs on unpack then insert your own code into their work
and fuck everyone that installs it.

Just saying!
Not that i'd do that myself, (much).eace: