Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
BoredPanda29

IS this safe?

Recommended Posts

So I have been testing out some of the scripts and what really has me worried is it looks like random people that have no idea what they are doing are just throwing in random ABC things and saying it must be safe! All this is doing is make bots stand out like a sore thumb and get very low xp rates.

On one example an agility bot it inserts an ABC break between every action. This makes the script 10x slower in getting xp and noticeably slower than all the other players who don't randomly stop in the middle of the agility course.

The other thing is the bot randomly examins things in the middle of training xp way too often. Sure maybe if you average out how many times people click examine that might be how often, but it certainly is not while normal people are training agility!

Share this post


Link to post
Share on other sites
Just now, BoredPanda29 said:

On one example an agility bot it inserts an ABC break between every action. This makes the script 10x slower in getting xp and noticeably slower than all the other players who don't randomly stop in the middle of the agility course.

ABC2 reaction times will reduce the xp / h to some degree.

They were implemented in an attempt to replicate the human inability to focus for a prolonged period of time.

However if you get 10 times less xp than you should, the script might have a problem.

Share this post


Link to post
Share on other sites
24 minutes ago, BoredPanda29 said:

Well maybe the ABC should be dynamic to the activity. I doubt people put the same pause between everything and I know no one waits thing long in agility.

It really is dynamic.

All ABC sleeps are generated dynamically based on multiple factors, one of them is the amount of time spent performing a certain action (for example cutting a tree).

 

Example:

This is the 12th time it chopped a tree:

JOTfIuy.png

 

And this is the next one:

yewaP6K.png

Edited by Einstein

Share this post


Link to post
Share on other sites

ABC2 reaction times in their current state are only supposed to be for activities that can not be calculated on how long they will take and even then the reaction times generated aren't ideal at all. This is pretty much summed up to mining, woodcutting, fishing, and combat. Agility does not fall into this category since you can calculate exactly how long it will take to traverse an obstacle. There's actually only 3 factors needed to calculate it, distance to obstacle, is run enabled, how long the agility obstacle animation is. Those 3 factors are calculated together into a consistent value and not a variable amount of time. So that agility script you're using shouldn't even have the ABC2 reaction times implemented, but they either added them because users requested them or were told to by an ill-informed administrator.

Edited by Encoded

Share this post


Link to post
Share on other sites
On 12/14/2017 at 4:45 AM, Encoded said:

ABC2 reaction times in their current state are only supposed to be for activities that can not be calculated on how long they will take and even then the reaction times generated aren't ideal at all. This is pretty much summed up to mining, woodcutting, fishing, and combat. Agility does not fall into this category since you can calculate exactly how long it will take to traverse an obstacle. There's actually only 3 factors needed to calculate it, distance to obstacle, is run enabled, how long the agility obstacle animation is. Those 3 factors are calculated together into a consistent value and not a variable amount of time. So that agility script you're using shouldn't even have the ABC2 reaction times implemented, but they either added them because users requested them or were told to by an ill-informed administrator.

+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
Sign in to follow this  

  • Our picks

    • This release will:

      Fix LG for both OSBuddy and RuneLite


      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)


      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)


      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users


      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)



      Upcoming updates:

      Improved CLI support


      Full Sentry support


      Much more
        • Like
      • 51 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      Fix resizeable minimap bug (Thanks @wastedbro)


      Remove Java 8 requirement


      Please note: TRiBot is not yet fully compatible with Java 10+




      Fix the break handler issues by ensuring the break handler thread never gets paused


      Fix broken settings hooks



      Upcoming updates:

      Improved CLI support


      Much more



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

      Add support for using custom F key bindings to switch between game tabs (Thanks @erickho123)


      Fix tab opening for "Skills" and "Kourend Tasks" (Thanks @erickho123)



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

      Fix an issue where breaks would stop firing


      Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls


      Fix an NPE in the Combat API


      Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen
        • Like
      • 21 replies
    • This release will:

      Add LG support for Runelite


      Fix NPCChat issues


      Fix a bug where the camera angle setter would just hold down a key for 5 seconds (the timeout)


      Slightly adjust the rotation via keys to be more accurate


      Add the ability for asynchronous camera movement via keys


      Make Camera rotation via mouse more fluid, with more antiban, and work much better in resizable mode


      Add a "Camera#setCamera" method, allowing the rotation and angle to be set in parallel


      Increase the likelihood of using the mouse for camera movements


      Add support for adjusting the camera to positionable entities (Positionable#adjustCameraTo)



      Upcoming updates:

      Improved CLI support


      Much more



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

    No registered users viewing this page.

×