Czar

Sure mate just tell me how it works, I'll be looking on youtube too.

Version 3.0 - Fixed dialogues - Made some improvements to speed Update should be live within an hour

Version 1.9 - Added world hop option - Added hop at X players option - Added hop when player says bot/botting/botter EDIT: - World hopping now prioritizes lower population worlds Update should be live within an hour!

Nice to see somebody else with fairy rings :P

I added a delay for clicking continue, it goes up to 10 seconds, then proceeds to what it was doing, however if it has stayed for longer, I will investigate the code

Good job mate, nice to see new scripters :P

Alright an update will be coming soon, try another fishing location until I get this fixed Ah wait, I changed the GUI to make it so you can ENABLE afking, which means it's already NOT afking, try without that option? maybe

Show me the console log, it just happened to me using another script (not mine). I will make a client bug report immediately.

Alright if it happens again just tell me how it performs and I will easily fix it, at the moment I will review the code for searching fishing spots

Hmm latest client? .42, and was the dialogue open until it logged out?

No but I am working on adding that location too, as a choice in the GUI. There will be a massive update today guys!

excellent job guys

What a clever lad

Thanks for the feedback, I will update the walking method. EDIT: Hmm in the meantime try raising the memory to at least 512mb, see if that solves the issue

You guys want the player to hop when there are 3+ players? (including yourself) So far, I am adding an option for hopping if somebody says 'bot/botting'

http://pastebin.com/raw.php?i=tzh4Zi18 Not really for speedrunning, but it is efficient af

Thanks for the feedback man also I don't think rock crabs drop bones, otherwise yes I can add bone burying support

Ohh lol here, this explains better than I can: http://osbot.org/forum/topic/57431-explaining-break-settings/ Don't bot for more than 12hrs/day, and if you want to avoid bans even more, use the mirror client

Ah I guess you can make it so if the closed door doesn't exist, then go to the SPIN case (use the spinning wheel) (lumbridgeDoor == null || area.contains(myPosition) to set the SPIN state, otherwise it will just walk to the room redundantly, when it can just click the spinning wheel and immediately start spinning ;)

You forgot to add spinningWheel.interact("Use"), that's why it's not doing anything

Since it is the first time you are running it, go to bank and have the items you need in your inventory, e.g. 20 trout, 1 camelot teleport then, click the button called 'Load Inventory' and it will save that inventory for the future, so every time you kill rock crabs and bank, it will take out those items. If you bring a camelot teleport with you (cammy tab) it will teleport, if you bring camelot spell runes, it will teleport using the spell. If you want to train ranged, bring some arrows/knives/whatever and run the script. The script does most of the work for you. Make sure you run the script while logged in.

Make a filter for the door with the following checks: - hasAction("Open"); - getY() <= Y (y being the y coordinate of the door closer to the stairs, not the second door for rune mysteries) if ^ that door exists, open it, if not, click the spinner and proceed with spinning. public static Filter<RS2Object> LUMBRIDGE_SOUTH_DOOR = new Filter<RS2Object>() { @Override public boolean match(RS2Object o) { if (o != null && (o.hasAction("Open")) && o.getY() < YYYY && o.getName().equalsIgnoreCase("Door")) { return true; } return false; } };

Hmm, you'll have to give me more information than that, try running the script now and see what happens, if nothing still happens, I will investigate the issue. I do have an idea though, which experiment spot did you go to? Did you change anything from that last run? I haven't made any recent changes, so if this script worked last time it should keep working and so on, also, make sure to use the latest client .40

Thanks mate, so far I think I've fixed the aggressive mode, other than that the script works fine. The aggressive option was causing problems a few versions ago, however I made some changes in v2.15.

Nope, but good idea