Alek

Scripters had 2 weeks to update their scripts.

The update log should be pretty self-explanatory so I won't bore you guys to death with all the backstory. All users should now have a fully functioning resizable mode event solver, hopefully there will be a lot confusion regarding this issue. Additionally there were a handful of menu, inventory, and spell changes that have improved InteractionEvent's stability even further. Oh and did I mention that mirror mode now receives the same Thursday updates as the core client (thanks MGI)? Changelog: -Deprecated Option constructor -Added Menu method getTooltip() -Deprecated Client method getTooltip() -Deprecated Client method getRawTooltip() -Updated ResizableMode Random Event -Added new Walking class (Deprecated, beta) -Updated Combat method isMultiway() -Updated Inventory method isItemSelected() -Updated Inventory method getSelectedItemName() -Updated Magic method isSpellSelected() -Updated Magic method getSelectedSpell() -Updated InteractionEvent inventory handler -Removed Tooltip Callback -Updated Lunar spellbook -Removed PositionPolygon -Removed PolygonArea -Removed utility.Area -Updated AreaFilter -Mirror Mode game updates are now automatic Version 2.3.94 Release -Additional mirror mode checks and verification -Updated random event activation -Updated preset points in IE Offline JavaDocs can be found at https://osbot.org/api/javadocs.zip Have a great weekend -The OSBot Staff

Item i; if ((i = getBank().getItem("Oak logs")) != null && i.getAmount() > 100) { System.out.println("We currently have " + i.getAmount() + " " + i.getName().toLowerCase() + " in our bank."); }

This is not a client bug or suggestion. Moving to general help.

This is what's available in the main client. Mirror mode could be overriding that check by forcing you to switch to fixed mode before you start the bot.

Private message me your steam so I can verify the SMFC.

There is a resizable random event now which automatically switches for you.

Even if all bots are banned by a human, there are automatic systems in place to flag a bot.

http://osbot.org/api/org/osbot/rs07/antiban/AntiBan.html bot.getMethods().getAntiBan().initializeModule();

http://osbot.org/forum/topic/60537-tutorial-simple-interaction-with-objects-and-npcs/

Read the Antiban API.

It's a pinned topic in the VIP section. There aren't much and this is not technically a VIP feature, just a nicety.

Due to the recent update 2.3.88 update, we're going to be running a few tests which will temporarily disable some scripts from starting for ~3 minute intervals. This should take between 1-2 hours.

OSBot 2.3.89: Patched up some additional SDN script conflicts with the new release, a majority of scripts should be back online. This was a very large update so please give scripters some time to update their code.

The new Area class will be bare bones for a while. Additional methods will be implemented over time and careful monitoring; trying to keep things clean.

Alright thanks, I still have your initial report (hidden). When I get a chance I'll review it, promise.

New Area API: This new Area class will be replacing (and eventually force the removal of) utility.Area, map.PolygonArea, and map.PositionPolygon. The benefit of having a single class versus multiple should be pretty apparent; versatility, mobility, and an easier API to understand. Many of the old constructors have been retained so all you have to do is change your imports. In addition, the new Area class supports plane checking and setting. The old area classes will be removed in early August, please start switching over if you are a scripter. Resizable Mode: No it's not Resizable Mode support, but a random event which will automatically configure your display settings to ensure that all botters are ready to bot. Some notable patches include an equipment item container fix, interacting with inventory items that are already selected, and scripts executing during the login/welcome screens. Changelog: -Prevented scripts from executing during login/welcome screens; code cleaned (2.3.85) -Added Equipment initialization to patch ammo/ring slots (2.3.85) -Deprecated PolygonArea (2.3.86) -Deprecated PositionPolygon (2.3.86) -Deprecated utility.Area (2.3.86) -Added map.Area class (2.3.86) -AreaFilter new constructor; PolygonArea (2.3.87) -AreaFilter new constructor; org.osbot.rs07.api.map.Area (2.3.87) -EntityAPI new method public E closest(org.osbot.rs07.api.map.Area area, String... names) (2.3.87) -EntityAPI new method public E closest(org.osbot.rs07.api.map.Area area, int... ids) (2.3.87) -InteractionEvent improved inventory handler (2.3.87) -org.osbot.rs07.api.map.Area(Position, Position) automatically sets plane (2.3.87) -Deprecated public E closest(org.osbot.rs07.utility.Area area, String... names) (2.3.87) -Deprecated public E closest(org.osbot.rs07.utility.Area area, int... ids) (2.3.87) -Deprecated public E closest(PolygonArea polygonArea, String... names) (2.3.87) -Deprecated public E closest(PolygonArea polygonArea, int... ids) (2.3.87) -Deprecated org.osbot.rs07.api.map.PolygonArea (2.3.87) -Deprecated org.osbot.rs07.utility.Area (2.3.87) -Removed PolygonAreaFilter (2.3.88) -OSBot Antiban not initialized by default (2.3.88) -Added Resizable Mode random event (2.3.88) -Finished replacing old area classes with map.Area throughout the API (2.3.88) -Updated map.Area reverse compatibility (2.3.89) -Updated ScriptExecutor pausing and CPU usage (2.3.90) -Distribution of mouse destinations based on Kantorovich's linear programming (@Maldesto 2.3.90) Enjoy your botting weekend. -The OSBot Staff

After ten years of fighting bots, I'm sure they have the technology to see past movemouserandomly() and checkrandomstats(). The random sleep times are the best (sarcasm): sleep(random(3333, 5473));

Not believing in magic tricks and snake oil.

This is in resizable mode, you need to be in fixed-screen.

The client has random event dismissing by default. In addition, this snippet does not check to see if the random is yours.

InteractionEvent handles a lot of the guesswork. getInventory().getItem("item").interact("Use"); getObjects().getClosest("object").interact("Use"); If you want to be fancy you can make each interaction in a boolean, check the result, and then handle any steps from there.

Is this the legendary Chuckle, founder and CEO of infamous PowerGP Ltd?

import org.osbot.rs07.api.Inventory;