See, you guys are getting the idea. The main concept your missing though, is it is not ONLY limited to web interfacing. I only referred to it, because its popular, its been done before, and this would allow even more power through that type of interface. People often write configuration utilities for bots to help setup config files. This could do it in one line. You could command the bot to enter a game. You could command the bot to perform a ban. Not only from other web interfaces, but from other applications, command lines, shortcuts, anything that will launch a URL. You can integrate a battle.net bot into so many different applications and services, its not even funny. Plus, its totally secure! There can be no "remote" control though a protocol listen on a local machine. It's like creating your own "localhost" which points to your local IP. This is your own URL that points to your own Application. If specifications were wrote, you could control 10 bots at the same time, on completely different servers, through one URL. One hit, one kill. Power. Endless Power. Non Exploitable. Perfect Sense. Say your bot uses local hashing, and it uses local hashing for a reason. If you didn't want users using BNLS, but still wanted to use it to check for updates, You could add support for your bot to connect to BNLS simply to check for updates. Instead of writing an entire new application to do this, you could do it from the URL. Create a shortcut, enter the bot URL (bot:checkupdate?client=STAR&SEXP)... What would take many, many lines in HTML and other web coding languages, could be done simply through a URL, and handled by the core application. Instead of, Web interface communicating with the application, instructing the application, waiting for a return from the application, then outputting again. With a URL, you could simply click a button or link, the application would handle it invisibly, and the web interface would do the work its already been designed to do... It's a really, really, really nifty concept...
