Protection:
I hesitate to discuss protection on forums as most users do not understand and have not worked in the security field, reverse engineering etc. but it is an important and hot topic. Of course everyone has an opinion, but they aren't really that useful and tend to create long circular arguments between the 2 camps (injection vs passive). Currently, of course, a new bot isn't detectable and wouldn't be of interest for probably some time. That being said our 'protection' is two fold:
1. Architecture - our application architecture is extremely passive - we do not touch the game executable or game space. Simple ask the pros, Hamut or Mercury and they will tell you it is far easier to protect a public bot that is passive. Simple put there are only a few ways to detect it and it isn't terrible hard to watch for. Undetectable: nothing is. Best case scenario: absolutely. Our app wont 'accidentally' get detected because of some missed hook in our code or a detection for another bot that encompasses a similar technique that we might be using, this cannot happen . Someone would have to get really serious and then we can meet their update as planned.
2. Private monitoring - the new trend in the post Glider world are private trip wire systems. Most are little more than a dead man switch duct taped to a hacker on the other end (if at all). We have a similar, but more automated system that watches not only for updates, but also communication between the game and client. We will bring the client down on patches as well as Module updates and reverse the code to ensure protection. Try our application and you will see we know what we are doing.
We have put a lot of time to build this application and have no intention of losing customers or money to ban waves. We are not a couple of part time coders or weekend warriors who decided to 'make a bot'. Security is very high on our list of priorities and we will address it professionally and aggressively.