Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Sell OSRS Gold
Usa

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

Recommended Posts

Also, when mark of grace spawns in this spot, the paint spams that it found a mark of grace, and it is picking it up, but it stands there and does nothing forever until you manually fix it. The red dot on mini map is where the grace is

 

naqu8kJ.png

 

This bug is still happening in v 5.0

Share this post


Link to post
Share on other sites

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
Guest
This topic is now closed to further replies.

  • Our picks

    • Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
        • Like
      • 25 replies
    • Come give us feedback on the next version of TRiBot!
        • Thanks
        • Like
      • 70 replies
    • TRiBot is looking to improve a lot of its customer relationship management, customer on boarding process, customer experience, design elements, community engagement and pretty much everything else you can imagine when it comes to marketing.

      Our goal: To ensure that the marketing done TRULY reflects the experience and does not shine an inaccurate light on what TRiBot is lacking in.

      So I ask, what do you love about TRiBot and what do you hate about TRiBot? What does O S Bot, Rune M8, PowR Bot and Dre amBot do better? (yes I purposely didn't spell it right 😂).

      Love, 

      RileyZ
        • Like
      • 23 replies
    • Over the last three weeks, I've been working on upgrading our server infrastructure. It's finally ready and is now live!

      Why?

      Increased reliability - less server errors


      Increased availability - less downtime


      Increased security - keeping us and you secure


      Increased capacity - ability to serve you better


      Increased speed - less waiting for things to load


      Faster development - server and service updates will come faster


      What are the changes?

      Move from a single AWS EC2 instance to AWS ECS (Elastic Container Service)


      Distributed computing


      Load balancing


      Git management of server files and filesystem


      Redis caching


      How?

      AWS ECS (with 10 EC2 instances)


      AWS ElastiCache (Redis)


      AWS Load Balancing


      AWS EFS (Elastic file system)


      Please bare with us as I continue to tune the server for maximum performance. Slow loading speeds may occur temporarily. I thank everyone for their patience.

      Please post on this thread if you experience any issues other than slow loading times.
        • Like
      • 51 replies
    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)


      Improve banking API (Thanks @Encoded)


      Adds methods for returning and using Java Lists, rather than arrays


      Slightly randomizes some hardcoded behaviour


      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable


      Other back-end improvements





      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Sad
        • Haha
        • Thanks
        • Like
      • 90 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...