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

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.

Sign in to follow this  

  • Our picks

    • 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
      • 61 replies
    • This release will:

      Add new internal framework for capturing exceptions


      Fix issue with not selecting the last column in world hopper (Thanks @Todd)


      Add a message about pin usage in Banking#openBank (Thanks @Todd)


      Disable the firewall by default (Thanks @Todd)


      Fix handling of the welcome screen after login (Thanks @Encoded)


      Fix wrong amount bank withdrawal (Thanks @Encoded)


      Fix Screen#isInViewport


      Fix Game#isInViewport (Thanks @Encoded)


      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)


      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)



      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Thanks
        • Like
      • 28 replies
    • 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
      • 64 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
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...