1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

RuneMate V1.0.0 - Beta 41

Discussion in 'Announcements' started by Cloud, Jul 31, 2014.

  1. Cloud

    Cloud Engineer

    Joined:
    Jul 28, 2013
    Messages:
    2,777
    Likes Received:
    1,124
    • Fixed RS3 collision flag generation (they're now 100% accurate)
      • As a result, RegionPaths are now functioning correctly in RS3 and may be used as an alternative to BresenhamPaths
      • This also means that Coordinate.isReachable, isReachableFrom, and getReachableCoordinates now function correctly in RS3.
    • Renamed getOrientation to getHighPrecisionOrientation.
      • getHighPrecisionOrientation is for internal use only and may be subject to removal without notice.
    The JDocs have also been updated, enjoy :)

    @Wyn please test your runespan script bot and let me know if things are working more smoothly
    @Exile please let me know if ExoWisp works better in this release :)
     
    Wizard likes this.
  2. Wizard

    Joined:
    Jul 27, 2014
    Messages:
    165
    Likes Received:
    10
    Sweet yo. ;)
     
  3. Neospacian

    Joined:
    Jul 17, 2014
    Messages:
    108
    Likes Received:
    8
    I hope Runespan works!!! xD
     
  4. Wyn

    Wyn

    Joined:
    Jul 10, 2014
    Messages:
    65
    Likes Received:
    7
    Still off.

    [​IMG]


    g.drawPolygon(target.getPosition().getBounds()) throws nullpointers even if null checked.
    Object interaction is failing for some GameObjects. Mouse not moving an inch.
     
    #4 Wyn, Jul 31, 2014
    Last edited: Jul 31, 2014
  5. Exile

    Joined:
    Jul 24, 2014
    Messages:
    188
    Likes Received:
    23
    Now the script bot can detect & click Wisps 99% of the time, but it doesn't detect the Energy rift anymore, something that did work before the update :p

    If you want to try it, there's a divi rift in Lumbridge, ID = 87306
     
  6. Cloud

    Cloud Engineer

    Joined:
    Jul 28, 2013
    Messages:
    2,777
    Likes Received:
    1,124
    It's likely position that's null, not the bounds.
     

Share This Page

Loading...