Alek

That's the only way goldfarmers survived during trade restrictions. They would hop on your account and do the transfers at GE.

I've been on a pasta salad rampage recently.

I understood the joke and found it humorous.

Pasta salad

That method is well known by both farmers and Jagex, same with dying in the wilderness which prompted the removal of PvP and the creation of revenants and Bounty Hunter.

Not quite:

The instant-hop injection method originated in an RS helper, not a bot.

Sounds about right. Minor first and then major for non-goldfarming accounts and major instantly for goldfarming. I could be wrong, but I believe that's how it works.

I might consider checking conditions in the walking event, however it will be when we're looking over the walking code again.

Unless you have a separate thread, no. It's the order of execution, how else would you be able to call code before it is even reached? We could have walking events accept break parameters, however I'm not sure if I want to create even more API which I have to maintain in the long run.

I think you were trying a bit too hard for the capital letters to be original. Personally I'm a huge fan of simplicity. The lettering besides the S, D, and g, are all very nice and the texture/glow were done pretty well.

Jagex added it as a feature, please read the News and Announcements: http://services.runescape.com/m=news/world-switcher--rotg-i?oldschool=1 The original way of instant-hopping brought into account a serious consideration of detection. After seeing this update I'm glad I stood by my decision not to make that update like all the other bots were doing.

For Mirror Mode related issues, please visit the mirror mode forum.

No limitations on OSBot for local, free, or premium scripts. Only limitation to free users is the amount of accounts you can run.

This is a core update, it affects both standard mode and mirror mode.

It was an inside job.

This update should not be coming as a surprise, I routinely monitor the game News & Announcements to ensure what we have reflects what is currently available. I did a check to see what scripts were affected and only a very small batch of scripts will break (less than three). Changelog: -Added Mouse method scrollUp() -Added Mouse method scrollDown() -Added RS2Widget method getBounds() -Updated LogoutTab logout() to account for world selection screen -Added WidgetSizeFilter -Re-wrote the Worlds API --Worlds no longer uses the XWorld instance --Worlds is now strictly based on instant-hopping --Worlds can be set as their short or long value (eg "2" or "302") ---This affects the settings hopper as well The API Docs have been updated! Happy Hopping -The OSBot Staff

Are you starting a new bot tab with a "Default" account? If so you need to use an account with your RS user/pass so it can successfully log you back in.

This update affects both normal and mirror mode. All updates to the client are "core updates", meaning that generally speaking the entire bot is affected.

This update is to try and bring mouse movements and interactions closer to near flawlessness. There are a few modifications I need to make, but this is definitely a great start in the right direction. The most noticeable change is interactions with large objects such as trees, dragons, etc. Additionally by popular request, the connection error from Auto-Login response code is now on a cycle. The event will take multiple fails before giving up instead of ending on the first attempt. Please expect another release either this weekend or early next week for World hopping and World instant-hopping. Please thank @Zach for his continued support. Changelog: -Added GraphicUtilities method getSuitablePointFor(Bot bot, int gridX, int gridY, int z, Model model) -Updated MoveMouseEvent to utilize new suitable point method --Patches a variety of issues specifically with large models such as trees and dragons -Removed multiple move attempts from MoveMouseEvent -Improved MoveMouseEvent movement algorithm --Patches divide by zero error as well -AutoLogin connection response code error runs on cycles instead of instant failure -Reverted inventory changes from 2.3.68 -Updated LogoutTab logout() to account for World Switcher being open -Added LogoutTab method worldSwitch() -Updated OSBot updater Happy Botting -The OSBot Staff

Was your contract 2 years? Our minimum is 4 years.

JROTC is usually for making rated officers aka pilots. Non-rated is useful, but they are dumping money on the ones who make them their bread and butter.

That dirt on your upper lip doesn't count.

You can either use the stream api afforded in Java 8, or run a for loop of all ground items.