Alek

On recent thought, I've decided against this in favor of it being handled by the scripter for various reasons.

It appears this was an issue that was solved in later updates of OSBot. If not, please delete your OSBot data folder.

Since this appears to be an issue with AutoLogin, I added a check to this solver for 2.3.59.

Wrong section.

All the Developers have been testing it to iron out any bugs (I personally haven't encountered any). We also typically make weekend releases so everyone from the team can make a meaningful contribution. Looks like we are on track and everything is running pretty stable.

Well if you look at the paint, it says the "Auto Login" is executing which is not correct, it should be "World Hopper". I'll take a look. That "extended delay" was cut in half from ~3 seconds to ~1.5 seconds. This is part of a cycle which may also have an overhead of about a second. At this point in time, I'm not interested in modifying the delay but I am already working towards improving the random event executor. But to answer your question, I'll definitely be looking into this around Friday.

This is not a community discussion. Please post in spam/real life.

Credits: @Asuna for showing me, my life is complete.

If Maldesto is forcing you to say this, just nod your head slowly... or not at all... I'll get the message.

-Have you tried it in the standard client? -Is ourOffers not returning empty?

Try downloading it directly from the site.

I don't think any scripts will be affected. Scripts that have world hopping currently however will not be using the new world hopper until the scripter updates his/her script.

This update is pretty large and encompasses something which everyone can benefit from. The FilterAPI now contains something called a singleFilter, returning the first matching result. With this, you don't have to wait for a collection to populate if you only need to filter for a single entity. On the subject of filters, you can now dynamically hop to worlds through the use of world filters in the new Worlds API. In this new API, you can scan for worlds using parameters of your choice such as if a world is P2P, has population of less than 1000, and is not a duel arena world. This will allow for stability in scripts that are reliant on world hopping. worlds.hopToP2PWorld(); Check out the World API here. And for the Worlds API click here. If you are unfamiliar with making filters, here is a quick snippet: Filter ActivityFilter = new Filter<World>() { @Override public boolean match(World world) { return world.getActivity().equals("Duel Arena"); } } Scripter note: The Worlds getAll() method behaves differently from other classes that extend FilterAPI. API such as NPCs can only return getAll() if you are logged into the game, however Worlds can only return getAll() if you are logged out. v2.3.57: -Added unregisterHook to RandomExecutor -Decreased RandomExecutor loop time in half -Added World API -Added Worlds API --Contains new world hopping methods -Deprecated WorldHopper -Added FilterAPI method singleFilter() -Added Widgets method singleFilter() -Added Widgets method getWidgetContainingText(id, text) -Added Widgets method getWidgetContaining(text) -Updated Dialogues API for general performance -Updated Bank API withdraw() method v2.3.58: -Updated Random Executor --Fixes a null issue people were having with world hopping -Other changes Have a great weekend! -The OSBot Staff

The correct amount of RAM will be allocated for what you need automatically. Only override it if you are very certain you know what you are doing.

It's almost as if Jagex has an infinite source of money so they can hire an employee for every clan chat in existence. Or a more realistic scenario, you were auto-muted.

Can't believe someone mad a cartoon of this so fast. Pretty funny too.

Not available in my country.

How is it called in your onLoop?

This looks like it was cheated on. Nobody smurfs an account up to LEM unless you are a Global; and the Global players are pretty well known in the community. With that said, either advertise this account as cheated or contact me on steam with a minimum of SMFC account. I'll leave my private messenger open on the forums. Source: I've been an LE/LEM.

I'm guessing you already checked your planes? Try using just InteractionEvent (it calls walking event methods), it checks for tile/object reachability which may also be an issue.

I used to do a fair share of luring. Most of the old-timers started off with the Wine of Zamorak trick. When lunar's first came out I did it instantly for the wildy group teleport which was pretty profitable. Common scenarios would be just trying to get someone to skull in the wilderness with my real life friend. Example: I find someone and bring him along with me for a duo pk trip. We would "find" my friend walking around in the wilderness and I would start attacking him. As soon as my duo partner attacked him for the skull, I would tb him and my friend with bring out the blitz. As far as luring/scamming outside of the game itself, I wouldn't be able to do it for moral reasons.

Looks like Maxi already handled this.

An overwhelming large majority of my private messages should not be sent to me. Common topics: -Things which should be addressed in the Script Update topic in the Scripter's forum -Errors which should be addressed in the Errors forum -Suggestions which should be addressed in the Suggestions forum -Disputes which should be addressed in the Disputes forum -Updating someone's specific script By having someone make a thread, I can easily track and manage each issue. Additionally, requests which are not in my department can be appropriately handled by a staff member.

I edited the title because it's misleading; we never made any promises that you would become invulnerable to a ban.

Or use localWalker.walk(area.getRandomPosition))? There's no sense in using paths for every scenario when you can have the walking event auto-generate one using DCPF.