Jump to content
Usa

[ABCL10][ABC2] USA Agility (Rooftops & Normal Courses) - Fastest Agility Script TRiBot has to offer!

Recommended Posts

V5.1 - 12/15/2013

- Now features DPathNavigating, uses Dijkstra's path finding algorithm on a smaller subset (30x30 radius from your Player) to generate paths on loaded tiles or the closest tile to the end tile you are attempting to create a path to, really cool and fast!

Share this post


Link to post
Share on other sites
  • [08:33:23] at scripts.UsaAgility.(UsaAgility.java:117)
  • [08:33:23] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  • [08:33:23] at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
  • [08:33:23] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
  • [08:33:23] at java.lang.reflect.Constructor.newInstance(Unknown Source)
  • [08:33:23] at obf.hB.run(jm:91)
  • [08:33:23] at java.lang.Thread.run(Unknown Source)
  • [08:33:23] org.pushingpixels.substance.api.UiThreadingViolationException: Component creation must be done on Event Dispatch Thread
  • [08:33:23] at org.pushingpixels.substance.internal.utils.SubstanceCoreUtilities.testComponentCreationThreadingViolation(SubstanceCoreUtilities.java:2048)
  • [08:33:23] at org.pushingpixels.substance.internal.ui.SubstanceSeparatorUI.createUI(SubstanceSeparatorUI.java:52)
  • [08:33:23] at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  • [08:33:23] at java.lang.reflect.Method.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.misc.Trampoline.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  • [08:33:23] at java.lang.reflect.Method.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.misc.MethodUtil.invoke(Unknown Source)
  • [08:33:23] at javax.swing.UIDefaults.getUI(Unknown Source)
  • [08:33:23] at javax.swing.UIManager.getUI(Unknown Source)
  • [08:33:23] at javax.swing.JSeparator.updateUI(Unknown Source)
  • [08:33:23] at javax.swing.JSeparator.(Unknown Source)
  • [08:33:23] at javax.swing.JSeparator.(Unknown Source)
  • [08:33:23] at scripts.UsaAgility$gui.(UsaAgility.java:2197)
  • [08:33:23] at scripts.UsaAgility.(UsaAgility.java:117)
  • [08:33:23] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  • [08:33:23] at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
  • [08:33:23] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
  • [08:33:23] at java.lang.reflect.Constructor.newInstance(Unknown Source)
  • [08:33:23] at obf.hB.run(jm:91)
  • [08:33:23] at java.lang.Thread.run(Unknown Source)
  • [08:33:23] org.pushingpixels.substance.api.UiThreadingViolationException: Component creation must be done on Event Dispatch Thread
  • [08:33:23] at org.pushingpixels.substance.internal.utils.SubstanceCoreUtilities.testComponentCreationThreadingViolation(SubstanceCoreUtilities.java:2048)
  • [08:33:23] at org.pushingpixels.substance.internal.ui.SubstanceSeparatorUI.createUI(SubstanceSeparatorUI.java:52)
  • [08:33:23] at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  • [08:33:23] at java.lang.reflect.Method.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.misc.Trampoline.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  • [08:33:23] at java.lang.reflect.Method.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.misc.MethodUtil.invoke(Unknown Source)
  • [08:33:23] at javax.swing.UIDefaults.getUI(Unknown Source)
  • [08:33:23] at javax.swing.UIManager.getUI(Unknown Source)
  • [08:33:23] at javax.swing.JSeparator.updateUI(Unknown Source)
  • [08:33:23] at javax.swing.JSeparator.(Unknown Source)
  • [08:33:23] at javax.swing.JSeparator.(Unknown Source)
  • [08:33:23] at scripts.UsaAgility$gui.(UsaAgility.java:2201)
  • [08:33:23] at scripts.UsaAgility.(UsaAgility.java:117)
  • [08:33:23] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  • [08:33:23] at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
  • [08:33:23] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
  • [08:33:23] at java.lang.reflect.Constructor.newInstance(Unknown Source)
  • [08:33:23] at obf.hB.run(jm:91)
  • [08:33:23] at java.lang.Thread.run(Unknown Source)
  • [08:33:23] org.pushingpixels.substance.api.UiThreadingViolationException: Component creation must be done on Event Dispatch Thread
  • [08:33:23] at org.pushingpixels.substance.internal.utils.SubstanceCoreUtilities.testComponentCreationThreadingViolation(SubstanceCoreUtilities.java:2048)
  • [08:33:23] at org.pushingpixels.substance.internal.ui.SubstanceButtonUI.createUI(SubstanceButtonUI.java:139)
  • [08:33:23] at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  • [08:33:23] at java.lang.reflect.Method.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.misc.Trampoline.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  • [08:33:23] at java.lang.reflect.Method.invoke(Unknown Source)
  • [08:33:23] at sun.reflect.misc.MethodUtil.invoke(Unknown Source)
  • [08:33:23] at javax.swing.UIDefaults.getUI(Unknown Source)
  • [08:33:23] at javax.swing.UIManager.getUI(Unknown Source)
  • [08:33:23] at javax.swing.JButton.updateUI(Unknown Source)
  • [08:33:23] at javax.swing.AbstractButton.init(Unknown Source)
  • [08:33:23] at javax.swing.JButton.(Unknown Source)
  • [08:33:23] at javax.swing.JButton.(Unknown Source)
  • [08:33:23] at scripts.UsaAgility$gui.(UsaAgility.java:2206)
  • [08:33:23] at scripts.UsaAgility.(UsaAgility.java:117)
  • [08:33:23] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  • [08:33:23] at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
  • [08:33:23] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
  • [08:33:23] at java.lang.reflect.Constructor.newInstance(Unknown Source)
  • [08:33:23] at obf.hB.run(jm:91)
  • [08:33:23] at java.lang.Thread.run(Unknown Source)
  • [08:33:23] org.pushingpixels.substance.api.UiThreadingViolationException: State tracking must be done on Event Dispatch Thread
  • [08:33:23] at org.pushingpixels.substance.internal.animation.StateTransitionTracker$ModelStateInfo.clear(StateTransitionTracker.java:166)
  • [08:33:23] at org.pushingpixels.substance.internal.animation.StateTransitionTracker.(StateTransitionTracker.java:194)
  • [08:33:23] at org.pushingpixels.substance.internal.utils.ButtonVisualStateTracker.installListeners(ButtonVisualStateTracker.java:72)
  • [08:33:23] at org.pushingpixels.substance.internal.ui.SubstanceButtonUI.installListeners(SubstanceButtonUI.java:238)
  • [08:33:23] at javax.swing.plaf.basic.BasicButtonUI.installUI(Unknown Source)
  • [08:33:23] at javax.swing.JComponent.setUI(Unknown Source)
  • [08:33:23] at javax.swing.AbstractButton.setUI(Unknown Source)
  • [08:33:23] at javax.swing.JButton.updateUI(Unknown Source)
  • [08:33:23] at javax.swing.AbstractButton.init(Unknown Source)
  • [08:33:23] at javax.swing.JButton.(Unknown Source)
  • [08:33:23] at javax.swing.JButton.(Unknown Source)
  • [08:33:23] at scripts.UsaAgility$gui.(UsaAgility.java:2206)
  • [08:33:23] at scripts.UsaAgility.(UsaAgility.java:117)
  • [08:33:23] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  • [08:33:23] at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
  • [08:33:23] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
  • [08:33:23] at java.lang.reflect.Constructor.newInstance(Unknown Source)
  • [08:33:23] at obf.hB.run(jm:91)
  • [08:33:23] at java.lang.Thread.run(Unknown Source) 

Came home to this today. Don't know what it's about but meh you might.

Share this post


Link to post
Share on other sites

V5.2

- Improved walking method speed, should increase overall speed across the courses.

- Fine tuned Rellekka for higher rates, getting about ~46K/HR over the past 10 minutes with 86 agility

 

4 more levels until I can add Ardougne!

  • Like 1

Share this post


Link to post
Share on other sites

This bug is still happening in v 5.0

 

The bug with mark of grace and not picking it up at seers actually led to one of my accounts being perm banned. Never botted anything else on the account. I was able to get it unbanned and when I logged in, my account was right in the spot it gets stuck at. Leading me to believe that bug got it banned. Hope it is fixed by now.

Edited by lolwutcool

Share this post


Link to post
Share on other sites

The bot gets stuck here frequently when trying to pick up Marks of Grace that don't spawn on-screen. I couldn't get a picture of that specific instance, but this is the spot that's causing me a lot of trouble.

 

http://s1364.photobucket.com/user/realsupersand/media/seersbug_zps40b81584.png.html?filters[user]=138631322&filters[recent]=1&sort=1&o=0

 

Edit: It also gets stuck frequently just after picking up the Marks and going to the next obstacle. It just says, "Got it!" and sits there for a while.

Edited by realsupersand

Share this post


Link to post
Share on other sites

The bot gets stuck here frequently when trying to pick up Marks of Grace that don't spawn on-screen. I couldn't get a picture of that specific instance, but this is the spot that's causing me a lot of trouble.

 

http://s1364.photobucket.com/user/realsupersand/media/seersbug_zps40b81584.png.html?filters[user]=138631322&filters[recent]=1&sort=1&o=0

 

Edit: It also gets stuck frequently just after picking up the Marks and going to the next obstacle. It just says, "Got it!" and sits there for a while.

I don't think he really cares about seers right now. People have been complaining about the Marks for awhile. He is only doing the courses in which he needs till he gets 99 then working on the others as it seems.

Share this post


Link to post
Share on other sites

The bot gets stuck here frequently when trying to pick up Marks of Grace that don't spawn on-screen. I couldn't get a picture of that specific instance, but this is the spot that's causing me a lot of trouble.

 

http://s1364.photobucket.com/user/realsupersand/media/seersbug_zps40b81584.png.html?filters[user]=138631322&filters[recent]=1&sort=1&o=0

 

Edit: It also gets stuck frequently just after picking up the Marks and going to the next obstacle. It just says, "Got it!" and sits there for a while.

If they are not on screen it should minimap click to the location, as for your second picture.. It's saying "Wall" which is entirely inaccurate  given that your current plane is not even 0. A little confused about that one.

Share this post


Link to post
Share on other sites

I'm confused too, man. I'm having a lot of problems with this specific course and the bot itself. It keeps failing all the randoms and logging me out-- and then, when I run this script, I end up stuck on that roof trying to collect a Mark that it refuses to walk to. I can't answer any of these problems because I'm a beginner with Bot scripting and all I'm doing is reaching out to the person who can. Plus, all of us paying 10$ to use this should get us something that works. It does a good job for the most part. It gets a little buggy if it misclicks and thinks it's on an obstacle and sometimes it doesn't pick up Marks right. Which I can understand, it is difficult to fix things like this. All I'm doing is reporting the problems I'm having.

Share this post


Link to post
Share on other sites

I'm confused too, man. I'm having a lot of problems with this specific course and the bot itself. It keeps failing all the randoms and logging me out-- and then, when I run this script, I end up stuck on that roof trying to collect a Mark that it refuses to walk to. I can't answer any of these problems because I'm a beginner with Bot scripting and all I'm doing is reaching out to the person who can. Plus, all of us paying 10$ to use this should get us something that works. It does a good job for the most part. It gets a little buggy if it misclicks and thinks it's on an obstacle and sometimes it doesn't pick up Marks right. Which I can understand, it is difficult to fix things like this. All I'm doing is reporting the problems I'm having.

I've shortened the distance on the mark of grace so it will walk to it if its more than 2 tiles away from your player, this looks like a case where the Camera angle and the conditions I set in the script created an issue for picking it up. I believe this will fix it.

Share this post


Link to post
Share on other sites

Rellekka seems to have a really low exp rate, It's a level 80 course which was stated to have a 58k exp rate per hour, I've been doing this course and only getting around 43k exp per hour just as much as i'm getting at Pollnivneach. I'm not sure why these are like that as there doesn't seem to be any bugs in the course just between each obsticle sometimes it takes a long time to move along.

Share this post


Link to post
Share on other sites

Rellekka seems to have a really low exp rate, It's a level 80 course which was stated to have a 58k exp rate per hour, I've been doing this course and only getting around 43k exp per hour just as much as i'm getting at Pollnivneach. I'm not sure why these are like that as there doesn't seem to be any bugs in the course just between each obsticle sometimes it takes a long time to move along.

What I've noticed is that even with 88 agility I seem to fail quite a bit, the highest rate i've seen was 48k/hr but as you've said.. it's basically never idle, always clicking. I think the 58k xp/hr rate is with a player clicking as fast as humanly possible and hovering over the anticipated locations of the next obstacle. Not much to tweak there, I've been running 80-88 there and done as much as I can.

 

v5.5 Uploaded

- Seers speed tweak, much faster now.

- Seers/Rellekka will now log out if you are not in the course area

- Mark of grace, fixed again had some improper logic however Seers has been tested and all mark locations work again

 

Thanks.

Share this post


Link to post
Share on other sites

 

I've shortened the distance on the mark of grace so it will walk to it if its more than 2 tiles away from your player, this looks like a case where the Camera angle and the conditions I set in the script created an issue for picking it up. I believe this will fix it.

 

That's what would happen when I would check on it. I would just move the camera so it could see it and then it would work just fine. I'm about to run it now and I'll be sure to let you know if anything goes wrong.

Edit: The sticky spot is fixed! It has picked up two or three marks there perfectly without getting stuck!! The only slight issue that I've noticed is after the Wall Climb and at the first Gap jump. You can see the obstacle and it screen walks over to it instead of just clicking it. This caused it to misclick a couple times but other than that there's no problems.

Edited by realsupersand

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • This release will:

      Fix login bot after today's game update (Thanks @JoeDezzy1)


      Fix latest in-game world hopping issues (Thanks @erickho123)


      Compact Settings UI and set location relative to TRiBot (Thanks @JoeDezzy1)


      Fix an older implementation of GrandExchange#getWindowState (Thanks @JoeDezzy1)


      Improve the preformance of NPCChat by only searching in certain interface parents (Thanks @JoeDezzy1)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      LG support for RuneLite


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 10 replies
    • This release will:

      Fix bytecode manipulation in order to prevent the modification of parameters within the Filter and Condition classes themselves (thanks @wastedbro)


      Fix NPE caused by non-null value in GE API (thanks @erickho123)


      Add and fix equals methods for api2007.types (thanks @JoeDezzy1)


      Modify Mouse#leaveGame to make the mouse leave the game from top, left, right, or bottom (thanks @erickho123)


      Add Entrana area to Ships API (thanks @erickho123)


      Fix raid prayers index/settings in Prayer API (thanks @erickho123)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 29 replies
    • This update will:

      Implement better canvas locking/synchronization mechanism


      Fix small Login API bug


      Remove the requirement for xbooting Java classes


      Use ExecutorService to perform canvas work in parallel


      Add "Account Management" game tab to GameTab API (thanks @Encoded)


      Fix NPCChat#getMessage (thanks @Encoded )


      Fix NPCChat#selectOption (thanks @Encoded )


      Fix Banking API after today's update (thanks @Encoded )


      Fix in-game world hopper after today's update (thanks @Encoded )



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 38 replies
    • This release includes:

      Fix updater bug which was causing a bunch of issues


      TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects


      Hooked login fields


      Improved the login bot


      Ability to recognize the banned/locked messages again


      Ability to read the current input for username and password fields


      If the username or password is already entered correctly, it won't be erased


      If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.


      If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.





      Coming soon:

      Skull icon fix


      Improve screen rate and responsiveness of the RS client (both regular client and LG)


      Much more
      • 33 replies
    • This release includes:

      Fix shift clicking option selecting


      Fix high paint delay settings saving


      Update prayer IDs for the quick select menu


      Remove RS3 support


      Fix hooks



      RS3 Support Removed

      The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

      For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

      If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
      • 25 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×