Molly

Please post a copy of the logger when things like this happen, it should list a reason as to why it logged out, and if it does not list the exact reason it may provide other clues. Like the OP for a trial, they are automated.

Looks like you have a trial now. That feature was removed because it wasn't super reliable, it would sometimes mess up and misclick or not realize the widget to interact with was loaded. I thought this caused the script to look too "bot-like" and I removed it to prevent accounts being put at risk. I can look into adding it back using some custom methods. Just made a Skype specifically for OSBot, adding you. Edit: Two contacts are coming up when I search that user, add me please. Skype: osbotmolly

Just added support for regular energy potions. This option will function as follows, if below a certain run, this number is fairly high, the bot will withdraw and drink an energy pot until it's either empty or above the target run amount. This option can be used in conjunction with stamina pots. If it is, the bot will withdraw a stamina pot only if below a certain run amount, this number is low, then withdraw an energy pot as well. The bot will first take one sip of the stamina pot then drink the energy pot until it's at exceeds the threshold for high run amount, or until the energy pot is empty. Once live the version number will be 1.1.

There's an issue with web walking that causes the agility shortcut in Ardougne to be buggy, after that is fixed it will be added. What does the logger say? Looting bag will not be used in combat, so until around 15 minutes after being at chaos druids in Edgeville looting bag will not be used. The druids are aggressive for roughly that amount of time.

Looting bag is being tested right now! This has taken much longer than I had hoped because of many issues arising, much of the code for the looting bag is custom methods I had to create. I have now pushed v1.2, this will include looting bag support, which works only in Edgeville of course. Please note that when using looting bag your logger is going to be spammed, this is intentional as it will help me troubleshoot possible bugs which arise, barring no bugs occur this spamming will be removed in due time. PLEASE BABYSIT THE BOT if you use looting bag, if you notice it runs well with the bag for some time by all means bot like you normally would. I just don't want any of you guys getting banned because you're using a new feature that may not be perfect just yet!

Are you saying it doesn't walk back to druids? Sorry, the typo is confusing because you could mean it doesn't walk to bank or walk back. If this is the same bug you reported yesterday a fix should be live by now and it should be correctly walking to druids. Thanks for these suggestions, and the proggy, I'm working on finishing up looting bag support and then I can look at some of those things. Trials should be automatically given within the next couple of minutes. My computer was down most the day, until about 5 minutes ago actually or else they would have been given quicker.

Fixed.

Looting bag support has been completed. Unfortunately I do not have access to an account right now to test it fully. I'd like to run tests with it for at least a few hours before I push the update live, if anyone has an account I can use to do this that would be great, if not I'll have one to do so by Saturday.

Looting bag work almost done! Just need to add a few more methods and test it a bit more and I can push the update.

Could you post what's in the logger when this happens please, I'm not having any luck replicating it.

I'll message you this Saturday when I will have plenty of free time to test, thank you!

Thanks for this suggestion, I'm going to be busy the next couple of days with work, but come Saturday I'll be working on adding a feature like this. Using a dose of stam pot every trip isn't optimal, I agree.

Not sure why I'm not able to receive messages, another user said that before as well. I currently am in need of an account to test blackjacking on, most of the code for it is written I just don't have access to an account right now to test it on for a few hours.

It will be out Wed/Thurs, looking like Thursday because tomorrow my last few parts for my new computer will be here and I'll be setting that up finally. Bug Fixes: Stuck upstairs at Ardougne fixed. I also looked into the bug you guys had reported at Taverly, I couldn't replicate it however. I removed some unnecessary checks and fail safes with walking by adding custom links in the web walker, hopefully that will prevent the issue from arising again.

Sorry I don't give out my Skype anymore, I prefer to be contacted via PM on the site. Just like the OP for a trial, they're automated. That bug appears to be a bug with web walking, is it happening on mirror mode only for you guys? Pathing in the dungeon is also web walker related, web is getting updates with every new client release so interactions with obstacles should become much better in due time. As far as switching attack styles, equipping new weapons etc that can be done, and I had been planning on working on a feature like that in another project of mine, it is no small job however and will take a bit of time. I'm taking a look at these bugs right now guys, starting with the one at Ardy as it will be the easiest to fix.

Shouldn't need to be cancelled for you to buy. Sorry bout your luck, that's the risk of botting.

LIke the OP for a trial guys, they are automated. 200k+ gold per hour

Like the OP for a trial, they are automated.

Post what the logger says please, it will say what the issue is.

Wow dick move.

Sure, just authed you a trial. Like the OP and one will be given automatically.

Need the log man, I added in a line of code that will tell me if the tabs were in fact detected. This will help me determine if they are being detected and not withdrawn or simply not detected at all.

Yeah, I found that out as well long ago when I wrote my thieving script. Trying to bank at Draynor and was wondering why it wasn't banking lol. I only pointed it out because the snippet you posted doesn't filter, it just checks that the object has the action prior to interacting. Theoretically if you walk into the bank and grab a booth getObjects.closest("Bank booth") you could end up continuously grabbing the same booth and thus would never interact with it if it didn't have the option. Resulting in the script just endlessly looping.

No problem!

Depending where you are banking keep in mind there are some bank booths that are closed, I think there is also one in Draynor bank that is sitting inside the bank. opposite the bankers that can't be used and it's named "Bank booth". I'd recommend grabbing objects around you and filtering them based on name such as "Bank booth" and checking to ensure the object has an action, in this case that action being "Bank". This will prevent your script attempting to interact with a booth that you can't actually use. Regular old sleep: sleep(random(150, 200)); Above code will sleep for a random time between 150 and 200 ms. Conditional sleep: new ConditionalSleep(Script.random(725, 925), 20) { @Override public boolean condition() throws InterruptedException { return getBank().isOpen(); } }.sleep(); Above code will sleep for a random time between 725 and 925 ms. However, every 20 ms the boolean will be evaluated and if true the sleep will end.