Given that game limits were recently re-enabled, Blizzard obviously uses rapid game creation as a metric of bot detection, or at the very least has the potential to do so readily available to them. It is undoubtedly one of the easiest methods to determine if someone is using an automated program to create games for them (whether it be DemonBuddy, AutoIt, or what have you).
To that end, I submit that we need protection from ourselves built into the DB client. The randomized game creation wait time is a solid temporary measure, to be sure, but it does not handle all scenarios equally well. Why? Because errors can and do occur. Problems with plugins, issues with profiles, and flaws in DB itself -- they all have the possibility to result in an endless loop of game creations, and after so long your account will almost certainly be flagged.
Yesterday I witnessed my Champion Farming profile enter and exit a game over and over until I stopped it. I have no idea why as I had never seen this behavior before. Thankfully, I was observing my bot at the time, but if I had been AFK when it happened, I have no doubt that I'd probably be banned in the very near future. I recently set my game creation delay to 3-7 minutes, but that should not be necessary when the profile itself takes 30+ minutes to complete.
What we need is something that can determine whether a run was successful or not. What we need is for DB to be able to detect the game limit notification and then stop trying for 5 minutes (or longer). What we need is a way to limit DB from creating more than, say, 10 games per hour. And so I am requesting what I believe to be an emergency feature necessary for the protection of all of us: DemonBuddy must be capable of both setting and detecting game creation limits, and then reacting appropriately - either by turning itself off, or at the very least by imposing a lengthy delay.
Thank you for your great product. Thank you for all your hard work. And thank you for reading and considering my proposal.