Am I the only person having serious problems with the bot lately? It pisses me off to no end. In the last 3 days, I have ran my fletching bot for 40 hours total and got probably 7k bows strung. I keep waking up/coming back from school to find that I am in Lumbridge, dead from the 500th failed random, and that my bot had just sat in Lumbridge for hours (might as well have put on an autotyper that said "ban me please").

 

I think the bot should have a failsafe where any time a random is failed, or your character changes location shortly after a random (specifically Lumbridge) OSBot should have a protocol to quit your script and log you out. It's one thing to have randoms failing, because there are 20+ randoms that all need to be scripted separately, but at least implement some sort of fail-safe. If it's impossible, feel free to berate me for being an idiot, but I feel like it would be relatively simple to add as an extension to the random activator.

 

With all that negative feedback though, I would like to thank Laz for pumping out all these updates lately. Although I am upset that my attempts at botting have sucked lately, I do understand that we only have one active, useful coder. I you Laz.

That's a good idea. Like you said though, not sure how easy it would be to implement.

You can write scripts to handle randoms intercepting it with try catch statements.

Use the Pest Control bank if you're fletching.

Yea ever since the whole banking update just about everything seems lesser then it used to.

^this. no snape bots are working well since banking update. its sad cause snape was mostly all I did. 

Ring of Life is your friend ;)

Use the Pest Control bank if you're fletching.

 

The problem with that is bot busts there. Had like 3 bots bot busted, 3 days in a row.

Ring of Life is your friend

 

Doesn't stop my bot from idling 10+ hours in lumbridge, which is what im actually concerned about.

 

Failsafe idea comes in handy.

I Support.

+1, it could managed in the randoms tab