Released V2.0.7

Discussion in 'Client Updates' started by Cloud, Apr 24, 2016.

    • Added Bank.open(LocatableEntity)
    • Added additional functions to the bridge that are now being used to make a variety of parts of the api faster
    • Made getting the root bounds of interfaces require less calls over the bridge.
    • Fixed some equals & hashcode methods
    • Adjusted some toString methods for a better presentation in the developer toolkit
    • Improved the handling of some exceptions occurring over the bridge
    • Replaced any RuntimeExceptions we were throwing with subclasses of it that are more appropriate for the situation.
    • Made the max mouse movement duration a part of PlayerSense
    • Fixed LocatableEntityQueryBuilder#unreachable/surroundingsUnreachable()
    • Improved handling of the execution of onStop
    • Throw an exception when building an InteractableRectangle that would overflow the integer bitspace. The primary purpose of this is so that I can see what exactly is going on when it's occurring for interface components in extremely rare situations.
    • Fixed a bug in Distance.between that was resulting in at least one call to Region.getBase() if either of the arguments was a LocateableEntity object, regardless of if was already stored in the cache or not. This fix resulted in a significant improvement in the speed of sorting entities, and as a result, .nearest() and similar calls when working with large sets of entities.
    • Optimized InterfaceContainers.getAt(int) by reducing the amount of data that gets transferred over the bridge from a boolean[] to a single boolean.
    • Fixed several ArrayIndexOutOfBoundsExceptions caused by an internal api attempted to decode -1.
    • Optimized GameEvent#getName() because it's string manipulation was actually slowing down the event handler slightly.
    • Added InterfaceComponentQueryBuilder#grandchildren(boolean) - by default it's set to true, but if you set it to false it'll only search the components during underneath the InterfaceContainers and will not invoke or search through InterfaceComponent#getComponents() for each of the InterfaceContainers components. Setting it to false is a major optimization in a lot of cases, often reducing the amount of components being iterated over by at least several hundred components.
    • Optimized ObjectDefinition#getName to not try to parse out the jag tags when it has the default value for a name which is "null".
    • Made the internal osrs interface option handler be more error resilient in regards to tab layouts.
    • Optimized osrs projection by applying the grandchildren(false) optimization in various places along with making some improvements to it in regards to tab layouts.
    • Added the same game object cache to osrs game objects that I'd previously applied to rs3 game objects, offering a reasonable speedup when doing operations on similar objects across multiple queries
    • Optimized ChatDialog.getContinue() on osrs
    • Rewrote the logic behind ActorQueryBuilder#targetedBy(Arrays.asList(null)). It now requires calculation of the target of each actor once instead of once for each Actor being analyzed (so O(n) -> (1)).
    • Made LootInventory.isOpen() immediately return false on osrs instead of trying to run the query. This was done because of MassFighter not doing proper checks and crashing as a result of it.
     
    Qosmiof2 likes this.
  1. Updated my client and Aplha fighter now wont start as a result. Was working perfectly before, now comes up with an error log which it wants me to submit to the coder, wont let me run the bot. Please fix.
     
  2. Awesome update!
     
  3. As a complete noob on bots, does this make banking for bots easier?
     
  4. Report that to the respective bot author.

    It may make it slightly more efficient.
     
  5. Yea some bots broke with this new update, is this on your end or bot author?
     
  6. Could be either at this point, I tested a lot of bots and was profiling throughout the entire night to tweak things on osrs extensively.
     
    RobinPC likes this.
  7. pi chopper/maxi woodcutter and celestial hunter wont start for me after the update

    java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
    java.rmi.UnmarshalException: unrecognized method hash: method not supported by remote object
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:353)
    at sun.rmi.transport.Transport$1.run(Transport.java:177)
    at sun.rmi.transport.Transport$1.run(Transport.java:174)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)
    at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276)
    at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:253)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:162)
    at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227)
    at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179)
    at com.sun.proxy.$Proxy8.int32_index_value(Unknown Source)
    at nul.IiiIIIiiIiii.int(rrb:230)
    at com.runemate.game.api.hybrid.local.Varp.getValue(vcc:184)
    at com.runemate.game.api.hybrid.local.Varp.getValueOfBitRange(vcc:138)
    at com.runemate.game.api.hybrid.local.Varpbit.getValue(wdc:190)
    at nul.IIIiIIiiiiII.int(xic:41)
    at nul.IIIiIIiiiiII.int(xic:33)
    at nul.IIiiiIiiiIii.int(lec:41)
    at nul.iiiIIIiiIIII.int(dcc:107)
    at com.runemate.game.api.hybrid.location.Coordinate.getBounds(jbc:19496)
    at com.runemate.game.api.hybrid.location.Coordinate.getInteractionPoint(jbc:9643)
    at com.runemate.game.api.hybrid.location.Coordinate.getInteractionPoint(jbc:20682)
    at com.runemate.game.api.hybrid.local.hud.Menu.click(xcc:247)
    at com.runemate.game.api.hybrid.location.Coordinate.interact(jbc:5552)
    at com.runemate.game.api.hybrid.entities.details.Interactable.interact(bj:65)
    at com.runemate.game.api.hybrid.entities.details.Interactable.interact(bj:154)
    at rm.Aux.int(v:173)
    at rm.nUL.enum(y:165)
    at rm.aUx.execute(y:254)
    at com.runemate.game.api.script bot.framework.task.TaskScript.onLoop(uxb:257)
    at com.runemate.game.api.script bot.framework.LoopingScript.run(ftb:198)
    at com.runemate.game.api.script bot.framework.AbstractScript.start(mub:102)
    at nul.IIiIIIiIiIIi.run(qbc:235)
    Caused by: java.rmi.UnmarshalException: unrecognized method hash: method not supported by remote object
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:293)
    at sun.rmi.transport.Transport$1.run(Transport.java:177)
    at sun.rmi.transport.Transport$1.run(Transport.java:174)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)
     
  8. You need to restart your runescape client.
    --- Double Post Merged, Apr 24, 2016, Original Post Date: Apr 24, 2016 ---
    V2.0.7.1 is now available. The only change is that when the bridge updates during a release (which is semi-frequent), we will now notify users that they need to restart their runescape client if the old bridge is detected. We do this by detecting the following error
    Code (Text):
    1. java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
    2. java.rmi.UnmarshalException: unrecognized method hash: method not supported by remote object
     
  9. tyvm
     
  10. u are the beast !!!
     

Share This Page

Loading...