Jump to content
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 update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 21 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
        • Like
      • 15 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      [NEW] Bug fix for intelligent banking


      [NEW] Improvement to the stability of LG over time


      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client


      [NEW] Fix LG login problems


      [NEW] Fixed re-sizable mode container bug


      [NEW] Fixed re-sizable mode mouse bug


      [NEW] Use of public constants in the Banking API


      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 12 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×