- Joined
- Aug 23, 2015
- Messages
- 1,961
- Thread Author
- #661
This bot got my account permanently banned, and on the first offense too! I'm positive this is the case because it's the only bot I've used on this account. Here is my story...
I decided to start playing OSRS again a week or two ago after a very long break. I created a new account, and started following OzirisRS's Iron Man v3 guide. I played all the way up to the Wintertodt section, and quickly realized how long it was going to take. I looked around and found Regal, so I decided to test the free version. I watched it the whole hour just to make sure I knew how it would run. After that, I bought $5 in credit and switched to the paid. IMO, there are several obvious issues that can result in detection and ban:
First, support for using Cakes for food is not great. It will eat the cakes in your inventory, but if you have any partial when it banks, it will deposit those and withdraw new whole cakes. This results in a bunch of partially eaten cakes in the bank. Definitely not human like...
Second, using the 'safe' tile was another bad experience. The bot clicks near the tree, walks over, the clicks the safe spot, walks over, and starts chopping. This is pretty obvious bot behavior if Jagex is watching your account.
Third, this one is more like general feedback, and probably didn't contribute to the ban. Using 'Intelligent' Fletching is not really that intelligent. The bot fletches and feeds the whole time, until the Wintertodt gets to about 10-12% and then it will stop Fletching and go feed even if you still have logs. I get that it's trying to maximize your total points by feeding what you have left before the round ends, but you should definitely add some customization options here. One for only fletch below 500, one for fletch X number of logs, ect.
All in all, I'm out the $11 for members, the $3 worth of RuneMate credit I used on this bot, and all the time it's going to take me to get a new account back to this point. I'm incredibly disappointed, and definitely frustrated about this situation.
Unfortunately there's always some risk when it comes to botting nowadays. Detection is much better than it was around 2008.
I'll be releasing a significant update to this bot in the near future that should change a lot of behavior and help prevent future bans.
Regarding your feedback points, only a couple dozen partial cakes are accumulated to 99, so I'm not convinced it's a real issue. It's not something that I can imagine triggering a ban.
I also don't like the safe tile option. Runemate's interactions have trouble walking there when people drop items (empty jugs) on the tile. I personally don't use it, but a lot of people like to so I leave it in.
The fletching mode does a better job of making the end-of-kill efficient, and will be even better after the upcoming update. Users get confused when there are too many options, which is why it's limited to the point it is.
If you choose to continue botting, I recommend the following guidelines. In my experience bans are very rare following these rules:
- Avoid botting on brand new accounts or accounts that were dormant for a long time. These are more heavily monitored.
- If you need to bot one of these accounts, vary the activities a lot or only bot 2-3 hours a day for about a week.
- Don't have very long and uninterrupted botting sessions. I like to do a maximum of two 4-hour sessions with a 1-2 hour break in between
- Don't bot the same thing for weeks on end - change it up a little bit
- Avoid botting agility for more than 2 hours a day every other day
Hey Snuf,
I just started using this bot yesterday. The first two times it worked great. The next couple of times late yesterday evening I kept getting stuck in the bank and had to shut it down because I couldn't get past 1 trip (2 kills). The same thing happened this morning and after messing around with it a bit, I got it to work. Needless to say I was charged for all of the 7 attempts that I had last night/this morning to try get the bot running. I didn't realize I would be charged for a full hour for those. I had to stop/start multiple times because it kept getting stuck in the bank and thought the start/stop would fix it. Here are my logs, the highlighted ones are valid charges. All others I was unable to run a successful session:
View attachment 10097
Sent refund