RuneMate V1.1.0

At RuneMate we use the major.minor.patch versioning system, so this next update is going to be the first "minor" update. Here are the changes thus far:

• Moved global navigation pathfinding to our server. This means that you will no longer be able to extend the default web. You can however still create your own webs and expand those as you please.
• Added the ability to hide and redisplay the client in the tray icon.
• Improved BeastOfBurden class and added a few additional utility methods (such as newQuery).
• Added Bank.withdraw/deposit/withdrawToBoB(SpriteItem, int).
  
• Made the Bank class close the search/withdraw x dialogs if they are blocking the item or button we are trying to click (RS3).
• Added a PaletteListener for detecting color palette changes efficiently.
• Added proper behavior to several methods in the ManagedProperties classes (both local instances and the synchronized instance).
• Fixed Summoning.FamiliarOption.setAsLeftClick (again).
• Fixed a negative position exception in the cache reader.
• Fixed an index out of bounds exception in clouse.
• Fixed a division by 0 error in the Menu class.
• Fixed maximizing the client on OSX and Linux.
• Added a fail safe so that the client won't crash if ClientUI.sendTrayNotification gets called on the Platform thread. I'm looking at you team celestial
• Fixed RS3 Target Gauges.
• Added more informative error messages for when a local bot is unable to be loaded. These messages include things such as not being able to resolve the main class as stated in a manifest, the lack of a public constructor, and the failure to extend the proper classes.
• Fixed OSRS Bank Pin Event.
• Added ActionWindow.isLocked (for inventory and equipment).

Please note that because I didn't start this log until far into the development of V1.1.0, many things have been left out. As they're discovered I hope that you guys will points them out

 

It's not something 95% of you will ever need to use but an example would be loading the static objects from a given area while you're elsewhere. That piece of data could then be used to manually calculate the collisions for unloaded regions. RuneMate used to have a GlobalPath class many months ago however it was removed because it required extended time periods for path calculations.

--- Double Post Merged, Apr 26, 2015, Original Post Date: Apr 2, 2015 ---

This thread has been reopened and updated with the new changelog for V1.1.0, some features that were originally going to be released in V1.1.0 ended up getting released in a minor build of V1.0.X (hence why the first few posts in this thread may no longer make sense lol).

 

Can you remind me what was wrong?

 

As in when it's moving towards the object or when it's moving away from it?

 

So just to clarify one more time, after you've already traversed the object and are moving towards the next vertex, it still clicks the previous object?

 

It was already done for the next build along with debug information for a lot of other errors. It's in the V1.1.0 changelog which is available in the Future Updates section.

 

Message me an OSRS account with a pin set.

--- Double Post Merged, May 10, 2015, Original Post Date: May 2, 2015 ---

An early access release of this build has been published. The changes include all of what is in this post except:

• Moved global navigation pathfinding to our server. This means that you will no longer be able to extend the default web. You can however still create your own webs and expand those as you please.
• Added proper behavior to several methods in the ManagedProperties classes (both local instances and the synchronized instance).

Unfortunately this includes the big feature, but rest assured it's coming soon. I'm back from a rough month and ready to finish up everything that was a work in progress

--- Double Post Merged, May 10, 2015 ---

Released a second Early Access build.
To account for a split between Legacy interface and combat settings, a new InterfaceMode class has been added that you can use to detect the interface state. In addition, CombatMode.getCurrent will now correctly return Legacy even if the InterfaceMode is still set to Modern.

 

You don't have to, but I still recommend doing it.

--- Double Post Merged, May 17, 2015, Original Post Date: May 10, 2015 ---

V1.1.0 (EA3) is coming now available.

It includes damage control from a recent RS3 update, improved handling of cloud based managed properties, a new LootInventory class which will be expanded soon, and many other bug fixes. In addition, the free bot session limits have been reinstated. @Arbiter can provide more information on that.

Only one more thing to address before the full release of V1.1.0

 

It looks like I may do one more release before the full release. It would include a Resources utility class (with things like getAsStream, getAsByteArray, getAsBufferedImage, etc), a fix for multi-plane traversal within the web, a new Area class, and other bug fixes.