I had the idea, since doing registration codes are annoying, what about this... User downloads the demo version of your game... They decide to purchase your game... You email them an expiring link to a download of the ''full version'' patch They patch their demo version and it becomes full version with all things updated to full version. Sound good? Ibuku weaponstudios.com

On the other hand...keycodes offer the exact same security...

1) A generic serial (which MANY programs/games use) can be posted on the net so that anyone can simply copy and paste this into their program.

2) A name generated unique key is the same way. Just post the name used and the serial used and anyone can copy and paste. Who cares that it is liscened to John Jim? You got it for free..and didnt even have to download anything.

3) Atleast a patch requires some downloading...and then that warez fiend has to find web space to post it to, since the link expires, etc. etc. it sounds MUCH more inconvience to post a patch.exe than a simple serial # that anyone can use at anytime.

If you can tell me why its harder for key code, then please do! Im trying to find the best way (and cheapest, with the development toolkit I used to make my game, I have to use reg software that makes the codes for me..which costs $100..so a patch would be alot cheaper for me - free)

Thanks guys.

Ibuku, Simple fix would be not to use a single key code or not to use a unique key code based on the name that the user enters.

Honestly, it isn''t that hard to create a Unique "lock" based off either the time it was installed, or possibly something like the CD-KEY for windows. Then once you make that unique lock, encrypt it for extra security and use a key that is longer than 10 bytes/characters.

Or to stop them from "cracking" the *.exe, maybe put some CRC in. There are *numerous* ways to slow them down. Those 2 methods you mentioned could be cracked by every Tom, Dick, and Harry.