For the last few days, I've been reworking the core real-time protection method. Instead of looking for specific windows text, titles or messages that fire the violation event, it's all based on a method that doesn't care what the windows text is. So, even if someone uses a computer with a non-English language, it doesn't matter if they try to open an "illegal" window. Phoenix will still protect the game.
Methods are being implemented to detect any software-based attacks and defeat them whether the Phoenix game is running or not.
I'm working now to get the methods to be extremely strict, yet allow system messages to show without shutting down the game..such as Firewall messages, registry notifications, error messages, etc. I have it working flawlessly now, I'm just putting the polish on the chrome.
Phoenix will definitely give you your money's worth. I'm also working on a method that allows you to use Windows Messenger, AIM or Trillian to communicate without compromising security. It's not easy to code, but I think you guys will appreciate the work when it's completed.
Fastburst and I have changed the ONLINE validation method entirely. In the Phoenix setup program, you can generate up to 99,000 unique keys at once to a file. When the web app is complete, you'll simply log in and update your game database with the file. From the web app, you'll be able to have multiple key definition files for multiple games, add/delete/modify key sets, etc. When the gamer registers online, the key is automatically "retired" so there's no need for you to interact. It's going to be really sweet when completed.
