Wait robotz u said if i get banned perm from this bot you will give me an account with 99 mage or did u mean enough hours for 99 mage because i have 5.5 blk marks .5 from this bot so far but i have reframed from using it because i dont wanna get another 5 and get perm banned and i still have 244:37 left on my bot
No lol, I mean if anyone loses an account through a fault in the bot, we give enough free hours to train a new account to 99.
Well this isnt as much a problem with the fact that people are getting banned because of it, its because theres some retards out there who are making new threads about it, and still ARE making new threads. A temp ban or something more servere needs to be put into place if you make another thread about MTA.
I'm sure threads being created at the moment are because people are baffled as to why the main thread's been replaced by this.
I also think people were probably unaware starting a thread about the MTA bot isn't allowed. I wasn't. One of the threads Wow Sucks complained about was speculation about the bot being highly detectable, created by someone who's never used the bot, in which respect it's very similar to this thread. I think rather than more serious action, make the rules a bit clearer about what's ok and what isn't, and direct whatever punishment to the people guilty of posting stupid threads, then you'll be making progress.
Thats what "Bot Busting" is. There isn't much you can do to avoid this as its not a detection system, but as robotzindisguise said the chance of you running into a J mod is quite low.
My suggestion to try and avoid being bot busted is only bot on the weekends in the UK Timezone as there will be even fewer J Mods (If any) online as its the weekend and being a Jagex is just a normal job after all.
Because Jagex know where to go in-game to find this bot, it does need more protection against bot busting than a scriptable bot for example. Towards the end of the life of Version 1, Jagex started bot-busting at the MTA, in reply we added an auto-talker.
The original auto-talker kept us safe for the past 2 months any time of day, it would reply to comments directed towards it, questions related to your levels etc, but because Jagex now have the source code - the v2.07 auto-talker no longer offers this protection, they know all the replies.
The new auto-talker (2.08) is safe though, and likely always will be, since it's now server-side - so as well as it's workings being a 'black-box' to Jagex (at best they can only see what is sent to server, and what is sent back), the server keeps track of all comments made to every user of the bot, including those from mods.
Tactics they were using to ID people included asking combat lvl (the bot could previously only give stats), but with version 2.08 the bot is now aware of it's combat level (although if you ask, you're more likely to get back something like, can't you tell? why are you asking? etc).
PS, I am still waiting for a full-screen screenshot in png format from anyone experiencing problems with 2.08. I need this to rule out or confirm my theory on why it's not working for some. It does need to be both full screen and in png (not jpg) format. Thanks, as soon as that's sorted out I'll deactivate 2.07 and we can all start using 2.08 without any problems from J-Mods.
