Jump to content
Aropupu

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

Recommended Posts

Aropupu

 

Hey man, just found a weird bug with the script.

 

It seems that the script does not start when you disable graphics in the client. Currently im using looking glass, and before I start the script, I click on client, and block user input and disable graphics to minimize cpu usage. I then start the script, and it withdraws all the items i require it to withdraw from the bank, but it does not start the course at all. I then untick "disable graphics" and only then it starts the course. I also notice that it does not go into afk breaks while graphics are disabled. The reason I know this is because the client says "will be going afk in the next 12 minutes", 12 minutes go by, and it doesn't afk. I then untick "disable graphics" and then it immediately goes into an afk break. 

 

Basically what im trying to say is that clicking "disable graphics" under client and having the script run while graphics are disabled will mean that the bot will not go into afk mode until it is unticked. Same goes for starting the course. I've only tried and tested this in the canifis course, maybe you could try to re-enact the bug to see what I mean. 

@Mark

The script does start without any issues when disable graphics is enabled. Either you didn't wait long enough or your Tribot client isn't working correctly. I tested this on LG and works every time I start the script while disable graphics is enabled. 

 

AFK mode doesn't work, because disabling graphics also disables the paint and the paint updates current time. I'll update a fix for this. Thank you for such a detailed report!

 

EDIT: Should be fixed in the latest version. Restart your script without using the rerun button to update it.

Edited by Aropupu
  • Like 1

Share this post


Link to post
Share on other sites

@Mark

The script does start without any issues when disable graphics is enabled. Either you didn't wait long enough or your Tribot client isn't working correctly. I tested this on LG and works every time I start the script while disable graphics is enabled. 

 

AFK mode doesn't work, because disabling graphics also disables the paint and the paint updates current time. I'll update a fix for this. Thank you for such a detailed report!

 

EDIT: Should be fixed in the latest version. Restart your script without using the rerun button to update it.

 

No problem, thanks for updating it so quick! 

Share this post


Link to post
Share on other sites

this script was absolutely worth my money, although I found one flaw were if you check on "progressive leveling" and deselect the courses you don't wanna do.. the script will go to them anyway. For example I deselected "canfis" and it tried to go there even though my account hasn't even done the quest..  

 

But overall the script is absolutely great, ran it for 11 hours one time. Received no bans! 

Share this post


Link to post
Share on other sites

this script was absolutely worth my money, although I found one flaw were if you check on "progressive leveling" and deselect the courses you don't wanna do.. the script will go to them anyway. For example I deselected "canfis" and it tried to go there even though my account hasn't even done the quest..  

 

But overall the script is absolutely great, ran it for 11 hours one time. Received no bans! 

@Generaltickle

Will need more information. I have tested disabling courses many times and I haven't been able to recreate this bug. Will send you a PM with questions.

 

my account just stood in 1 spot in pollivniech overnight it stayed logged in, not sure what to think but great script so far got 80 agility in a couple of days

 

edit: is it worth using turbo mode?

@kailax

Without a picture of where it stood or any client debug information, I cannot do anything about this issue. It's impossible to know what could have caused it without any information.

Edited by Aropupu

Share this post


Link to post
Share on other sites

@Generaltickle

Will need more information. I have tested disabling courses many times and I haven't been able to recreate this bug. Will send you a PM with questions.

 

@kailax

Without a picture of where it stood or any client debug information, I cannot do anything about this issue. It's impossible to know what could have caused it without any information.

i understand i was just letting you know, i just switched to relekka course because i was doing it through my phone so didnt bother taking pictures etc.

Share this post


Link to post
Share on other sites

not sure why but every time after 6+ hours the script auto stops then i need to restart the client twice for it to actually run the script again

@kailax

You should check you client debug and bot debug for the reason.

 

If I had to guess I would guess it's caused by the 6hr logout that is in Runescape. Your Tribot client is unable to log you back in and eventually ends the script.

 

If you haven't chosen any account information before you start the script, you should do that. If you are using autorelog, make sure it gets your account information correctly before starting the script.

 

If the tribot client freezes or something like that, it's a Tribot issue.

Edited by Aropupu

Share this post


Link to post
Share on other sites

This will be my first post and review on these forums, 

This script is truly amazing. There probably isn't a better script on the market for Agility and it's very well priced. 
I used this script from 30-70 Agility (so far) and it only took a few days of moderate use in accordance with my usual playtime. 
I never ran into any problems.
The script can be very personalized and honestly I can't see how they would catch someone unless they were abusing it. 
Since I still have some time left on the script I might shoot for 80 Agility, but who knows.
All in all it was completely worth the money because I hate agility but love it's perks. 

On a side note, scripts sure have come a long way haven't they...
 

  • Like 3

Share this post


Link to post
Share on other sites

Got banned using this script for 10 minutes on my main. gf me.

Most likely a delayed ban. 10 minutes would most likely not be enough for bot detection to kick in. It's also known that Jagex does delayed bans to not reveal what got you banned.

Edited by Aropupu
  • Like 3

Share this post


Link to post
Share on other sites

used this script for about 5 hours , two hours max at a time , havent botted anything else in months, did about 25 hours of legit zulrah between botting , got banned

 

wouldn't really recommend this if you're not wanting to risk banned

25 hours of legit zulrah.... ok.

  • Like 3

Share this post


Link to post
Share on other sites
18 hours ago, jimy said:

used this script for about 5 hours , two hours max at a time , havent botted anything else in months, did about 25 hours of legit zulrah between botting , got banned

 

wouldn't really recommend this if you're not wanting to risk banned

It could be that Jagex detected the change in pattern when and if you did zulrah legit. No way to know for sure, only Jagex would know why you got banned. There are plenty of possibilities for why you got banned.

I have given the users of this script all the tools that I could think of they can use to prevent bans and it's up to you to use those tools (=options in the GUI to customize). If you feel like the script is still missing something, please let me know.

Edited by Aropupu
  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, kuh47 said:

The seers teleport is glitched. It miss clicks a different spell, then can't click the cammy tele then fails to log. Please fix. Thanks.

Please be more specific when you report bugs. Tell how often it happens and maybe take a picture of the situation. 

Tribot is responsible for clicking on spells. If it missclicks, I can't really prevent that from happening. I can only add a failsafe for it. There should now be a failsafe that will recognize if it missclicked on another spell.

Share this post


Link to post
Share on other sites
On 3/19/2016 at 11:40 PM, Aropupu said:

Please be more specific when you report bugs. Tell how often it happens and maybe take a picture of the situation. 

Tribot is responsible for clicking on spells. If it missclicks, I can't really prevent that from happening. I can only add a failsafe for it. There should now be a failsafe that will recognize if it missclicked on another spell.

It's occasional, not consistent but could alarm jagex, because the bot fails to click the cammy tele then tries to right click the log out button and doesn't log out so it just keeps spamming right click log out. I've so far ran the script for 20 hours & so far nothing has happened. I'll let you know if the problem arises again, cheers

  • Like 1

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 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
        • Like
      • 27 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
        • Thanks
        • Like
      • 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
        • Thanks
        • Like
      • 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.
        • Thanks
        • Like
      • 25 replies
    • Please welcome our new developers, @JoeDezzy1, @erickho123, @Encoded, and @wastedbro.

      These members will be responsible for working on, maintaining, and improving TRiBot.

      This means that bug fixes and improvements will now come at a much faster pace! We're committed to providing users with the best botting experience possible!
        • Thanks
        • Like
      • 30 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×