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

Sell OSRS Gold
Aropupu

[ABCL 10] [ABC2] aAgility v2 [ALL ROOFTOPS]

Recommended Posts

Before purchasing this script, please try the free trial first. You can get a free trial in the repository. It will give you an idea how it works.

Make sure you have the normal spellbook enabled. (home teleport is used in course traveling)
Make sure ROOFS ARE TOGGLED OFF in Runescape's settings.

The script can be found from the repository:
https://tribot.org/repository/index.php?id=329

Features:

- Supports 13 courses.
- Can travel to all the courses except Ape Atoll as of yet.
- Can bank for energy potions, stamina potions and food. 
- Many optional antiban features that you can enable (afk mode, worldhopping mode etc.)
- Progressive leveling (autoleveling 1-99), which will change courses when you reach the appropriate level. Needs to be enabled!
- You can affect how the script goes through the agility course.

Normal courses:

  • Gnome Course
  • Barbarian Course
  • Wilderness Course
  • Ape Atoll Course:

Rooftop courses:

  • Draynor Village
  • Al Kharid
  • Varrock
  • Canifis
  • Falador
  • Seers' Village
  • Pollnivneach
  • Rellekka
  • Ardougne
     

Autoleveling [PROGRESSIVE LEVELING 1-99]

 

- Will change course automatically once you reach the required level. Needs to be enabled in settings before it works. Rooftops are automatically enabled. Only barbarian, wilderness courses need to be manually enabled. You can disable some rooftop courses if you want.

- If you start the script in Wilderness, autoleveling is not supported. Same applies if autoleveling takes you there after you reach the required level for it. The script will not travel away from wilderness.

- Traveling to Ape Atoll is not supported right now since very few people would need that as a feature anyway.

- Will use certain teleport items/tablets/runes when switching courses in the autoleveling mode. Support for amulet of glory, ring of dueling, runes and tablets. Check traveling settings to enable them.

Are you having problems with the script?

 

Easy way to solve most issues with tribot is to use the following tool: (this will delete hooks.dat, jagex cache, lg client related cache etc. for you)
https://tribot.org/forums/topic/80611-java-executable-delete-hooks-and-jagex-cache-and-a-few-other-things/
Make sure you close all tribot clients and runescape clients before you use it so it works properly!

You should try the following:

- Make sure your roofs are toggled off in Runescape settings.

- Simply restarting your Tribot client can sometimes help too. Also restart your Looking Glass client if you are using Looking Glass. Close all windows of Tribot and then restart it. It's recommended to restart a few times to make sure all hooks get updated, especially after Runescape has updated. Let Runescape load after each restart.

- If you are using Looking Glass with a client that has plugins, please try disabling plugins since some of those could interfere with Tribot's functionality.

- Make sure you have "Restart client on update" DISABLED in Tribot's settings. If it's enabled, it can cause problems after Runescape updates.
 
You can do the following all in one before restarting your client:

- Try clicking on File ---> Delete Cached Clients and restart your Tribot client.

- Try going to litemode in Tribot's settings and restart your Tribot client.

- Disable "Use Hook Storage" setting in Tribot settings.

- (You can skip this step if you decide to do the next one) Please try deleting hooks.dat and/or general.ini files from your .tribot folder. After this restart your Tribot. (close all windows)

- If removing hooks.dat/general.ini didn't work. Try reinstalling Tribot by deleting your .tribot folder and then restarting Tribot. Will reset your Tribot settings, consider doing a backup. Check this: https://help.tribot.org/support/solutions/articles/36000017490-how-to-fix-common-errors-by-deleting-the-tribot-folder

- Some people have also reported that deleting Jagex Cache can fix some issues. Here are steps to delete it: https://support.runescape.com/hc/en-gb/articles/360001441169-How-to-clear-your-cache-

if all else fails, please post a proper bug report:
- Describe the issue properly

- Send me your settings. You can get your settings by going to your .tribot folder and opening aAgility2_settings file in notepad. Then just copypaste all the text inside it here. You can get to your .tribot folder easily by going to File --> View local scripts folder in your tribot client and then going a few folders back from there.

- Tell me about your setup. Are you using looking glass? If you are, what client are you using? Are you using the script in resizable mode or fixed mode? Screenshot of your client when the issue is happening.

- Send me full client debug and bot debug information after the issue happens. You can copypaste both by doing the following:

DzdslQF.png

 

Settings information and help:

 

AFK mode instructions:

 

 

THIS FEATURE WORKS IN SECONDS.

You can choose how many seconds the script will AFK From A to B. By default it's from 0 to 300.

Common: The most common value. It will randomize the AFK time around this number. By default it's 30 seconds.
THIS NEEDS TO BE IN BETWEEN THE MIN MAN MAX VALUES.

Variation: How much the common value will vary. By default it's 15 so with the default settings it will vary between 15-45 seconds. This doesn't mean it will always be between 15-45, it just means that it will most of the time be between those values.
THIS NEEDS TO BE IN BETWEEN THE MIN MAN MAX VALUES. THE ENTIRE VARIATION 15-45.

Timeout: How long will the script wait minimum before AFKing again. This time will be randomized with the randomly generated seed from your account's name.

Mouse movement: You can choose if you want the script to move its mouse off-screen sometimes/always/never when being AFK.

Even if you have the exact same AFK settings with two different accounts, they will be randomized differently so it will not be exactly the same. The script generates a seed from you account name and will use that to determine the randomization.

The script will disable the login bot until the AFK sleep time ends. This means it will not attempt to login while it's being AFK.

Worldhopping (antiban) mode instruction:

 

 

THIS FEATURE WORKS IN MINUTES.

You can choose how often the script will worldhop to another world based on a timer in minutes. Works in the same way as the AFK mode.

From A to B: The script will randomize the value between these numbers so if you want the script to wait at least for an hour until worldhopping, you'll just add 60 - 90, which means from 60 to 90 minutes.

Common: The most common value. It will randomize the worldhop time around this number. By default it's 75 minutes. This value needs to be between the min and max value, otherwise the script might freeze.

Variation: How much the common value will vary. By default it's 10 so with the default settings it will vary between 65-85 minutes. This doesn't mean it will always be between 65-85, it just means that it will most of the time be between those values. The entire variation needs to be in between the min and max value, otherwise the script might freeze.

Even if you have the exact same worldhopping settings with two different accounts, they will be randomized differently so it will not be exactly the same. The script generates a seed from you account name and will use that to determine the randomization.

Action priority:

 

Here you can select which actions the script will prioritize when doing the course. If first priority is camera rotation, the script will check if it can rotate the camera, if not, it will try the second priority action. You can also choose how common those actions are.

- Disable camera rotation: will disable camera rotation done by the script, but not hover camera action. Tribot's antiban will still rotate the camera occasionally

- Disable screen tile clicking: Will disable clicking on screen tiles (getting a random tile near the next obstacle and clicking on it)

- Disable minimap clicking: Will disable occasional minimap click prioritization. The script will still click on the minimap if it's required or as a failsafe.

Hovering:

 

Disable hovering delay: Will disable a small delay in the hovering method. It will make the script check for hovering more often, which should make it faster but can cause problems too.

Disable screen tile hovering: Disables hovering over screen tiles when they are visible but the obstacle is not.
Disable minimap hovering: Will disable hovering over the minimap if the script is going to use minimap to go to the next obstacle.
Disable camera rotation while hovering: Will rotate the camera while still going through the previous obstacle.

Enable faster clicking after hovering: Will make clicking more faster if the script has just hovered.

Enable right-click hovering: Will occasionally or always right-click on the next obstacle and then select the option when it's time to click it.

Alching:

 

Have the items you want to alch in your inventory. Go to Debug --> Inventory in your Tribot client's menu. This will show IDs for all items in your inventory.

Then go to aAgility's settings. Behavior --> Alching. Input the ID(s) of the item(s) you want to alch into the Item IDs field (in the same format as 0,0,0,0 for example 5648,6678).

Enable "Cast alchemy spell while doing agility" checkbox and any other settings you wish and start the script.

Maximum alchs per obstacle allows you to make the script alch more than once before every obstacle and it's randomized around the number you input. Don't put too high values because the script will alch more or even too much with high values. Max I would put is probably 5. The absolute highest value I would put myself would be 7-8.

Always precast alchemy while in the previous obstacle will always precast alchemy while in the previous obstacle and you can override ABC2 (tribot's antiban), which prevents it from doing it all the time otherwise.

Enable more cast randomization = Doesn't affect the script much. Only affects alching while walking (does it start alching before it start walking more often etc.)

Random settings:

 

You can decide how the script handles camera movement. By default it uses the improved method that is the fastest method. You can choose the method controlled by Tribot (will use both middle mouse button and arrow keys) or just one of those.

You can also change the default clicking method, which is not recommended unless there are problems with the current clicking method. The default clicking method is far more superior and faster and more accurate.

You can also disable the xp failsafe. The xp failsafe is a failsafe that will log you out in 3 minutes if you don't get any xp in that time. You should only disable it if you are having trouble with it (it doesn't work properly etc.)

 

 

aAgility v3 [BETA]:

Spoiler

aAgility v3 is the next version of aAgility and is in BETA which means that it's still in testing and can have more issues than normal. This version is also constantly changing so new issues/bugs might be introduced by each update out of nowhere very often. Please keep this in mind before using the beta version. ONLY USE THIS IF YOU WANT TO BE A TESTER AND PROPERLY REPORT BUGS!

You can access the beta by clicking on the button that you can see when you start v2.

V3 also includes Brimhaven Agility Arena support now. Recording is not and will not be supported in Brimhaven.

How does recording work?
When you record data for the script to use, it will be used in the decisions and actions the script makes. This doesn't mean it will exactly copy all your actions in the same order or in the same way. It will use your data as a reference and base its actions on it which is also affected by randomization. To record data you simply press the start recording button and start doing the course when the script is recording. The script will record things like delays between actions, hovering, right-click hovering, minimap movement, screen tile movement, camera movement etc. Recorded data usage is constantly being improved and all playstyles might not be supported in the best possible way. Please report issues properly. Things like mouse movement itself and clicking actions are still handled by Tribot.

How much data should I record?
The more data you record, the better. I have disabled restrictions (minimum amount of recorded data) on this for testing purposes but I strongly recommend you to at least record 10 laps of data for each course. There's no way to know how much data you should record exactly, but more is always better.

Can I use v3 without recording data?
Yes

Things missing from v3 that are most likely going to be added:
- Alching (not recommended to record yourself alching yet until fully supported)
- Courses: Werewolf course, wilderness course, ape atoll course, barbarian course

Will write more info about possibly unclear settings below when I get around to doing it.

Camera settings:

Spoiler

To help you understand how the angle degrees work etc. you can enable Debug --> Camera in your Tribot client. It will show you the current rotation and by rotating your camera you can see how much it changes.

Max range adjust how much the camera rotation made by the script can differ from your recorded data. If you put it at 30 degrees, your camera rotation can have a maximum randomization of 30 degrees in both directions. Same applies for angles.

Randomization slider adjust how much the common randomization is out of the max range. So if your max range is 30 but your randomization is 50%, it will most of the time randomize the camera rotation about 15 degrees in both directions from the recorded data. Same applies for angles.

Increasing camera rotations means that the script will increase camera rotations between actions. This is useful if you didn't rotate the camera much because the camera was usually at a certain angle but you want it to rotate camera more if the rotation is different from when you recorded. Because the script also records the angles you click the obstacles in, it will be able to use your recorded data to increase camera rotation.

Arguments:
lastv3 = start v3 without GUI

 

Script arguments:
last = Will use the last saved settings. When you use this argument, the script will start without a GUI.

 

Please report any bugs properly. Don't just say something doesn't work or gets stuck. Explain as much as possible about the problem you are having. Taking a picture of the problem happening and showing it to me always helps too!

Edited by Aropupu
  • Like 8

Share this post


Link to post
Share on other sites
Array

does it tele to apeatoll?

Already bought

Agi was one of thefew prems i was missing.

Imo if i were you make Agility free bot only barb + gnome.

 

6$ is 2-2.5M on 07.

 

if you can'tget that you shouldn't get to do agility.

 

It doesn't tele to ape atoll but I can add it if you tell me where it teleports your account in Ape Atoll.

 

About the free version: I will be removing Ape Atoll from the free version soon. Wilderness will stay in it tho.

Edited by Aropupu

Share this post


Link to post
Share on other sites

It teleports you to where the king monkey is, right above the altar where people train on the monkey guards, up those stairs. 

 

Im at ape atoll now and i have been running fine but now im at 1 lobster and about 4 pineapple slices and my bot stops, i tried restarting bot with custom ID of the pineapple slices and the eat option lobsters but hes not moving. I ran the course and the camera corrected but hes not clicking.

 

EDIT i changed the way it eats, i have 1 lob left but it quit even though it had pineapples to eat as well. So under the "Eat option" i left it alone and just hit use knife and entered the pineapple ID. Now it works. I guess it stopped because i was low on lobsters even though it picked pineapples and sliced them.

Edited by DroDude

Share this post


Link to post
Share on other sites

It teleports you to where the king monkey is, right above the altar where people train on the monkey guards, up those stairs. 

 

Im at ape atoll now and i have been running fine but now im at 1 lobster and about 4 pineapple slices and my bot stops, i tried restarting bot with custom ID of the pineapple slices and the eat option lobsters but hes not moving. I ran the course and the camera corrected but hes not clicking.

 

EDIT i changed the way it eats, i have 1 lob left but it quit even though it had pineapples to eat as well. So under the "Eat option" i left it alone and just hit use knife and entered the pineapple ID. Now it works. I guess it stopped because i was low on lobsters even though it picked pineapples and sliced them.

 

There must be something wrong with the way I coded it. I'll go through the code and find out what's wrong.

 

EDIT: I forgot to include pineapples in the banking check so that will be fixed soon.

 

UPDATE: I updated the script to fix pineapples and banking. If you have a knife, the script will no longer attempt to bank unless you are about to die and you have no pineapples.

 

I also added the Ape Atoll teleport as a method for deathwalking/banking. You have to choose it as the deathwalking method so the script knows to use it while banking too. I have not tested the usage of the teleport myself because I don't have the requirements for it. It should use it properly and I did test that the script can find its way from the monkey in the temple.

Edited by Aropupu

Share this post


Link to post
Share on other sites

There must be something wrong with the way I coded it. I'll go through the code and find out what's wrong.

 

EDIT: I forgot to include pineapples in the banking check so that will be fixed soon.

 

UPDATE: I updated the script to fix pineapples and banking. If you have a knife, the script will no longer attempt to bank unless you are about to die and you have no pineapples.

 

I also added the Ape Atoll teleport as a method for deathwalking/banking. You have to choose it as the deathwalking method so the script knows to use it while banking too. I have not tested the usage of the teleport myself because I don't have the requirements for it. It should use it properly and I did test that the script can find its way from the monkey in the temple.

 

Awesome, going to let my bot run until it "may" die? lol

Share this post


Link to post
Share on other sites

Q90ejCy.png

 

Proggy I got on alkharid rooftop :D

 

Thanks, even though the proggie isn't that long. :)

 

You are actually using a buggy version of the al kharid course, because the update to fix some issues still hasn't gone through in the repository. I wonder what's wrong with the repository again.

Share this post


Link to post
Share on other sites

Thanks, even though the proggie isn't that long. :)

 

You are actually using a buggy version of the al kharid course, because the update to fix some issues still hasn't gone through in the repository. I wonder what's wrong with the repository again.

 

will keep it on as long as I can. :D

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • 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
      • 50 replies
    • Come give us feedback on the next version of TRiBot!
        • Thanks
        • Like
      • 86 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
      • 25 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...