Jump to content
TRiLeZ

Reaction Timing [Data Collection]

Recommended Posts

Hello community,

 

I am starting a new data collection project for reaction times. I'll use this data to adjust the formulas for calculating sleep times before clicking objects/NPCs/etc, which should make TRiBot have more human-like delays.

 

To take part in this project:

  1. Activate this script.
  2. Run the script.
  3. Play RuneScape. See below for further instructions.
  4. After at least 20 minutes of playing (try for at least 1 hour), stop the script. The script will then generate a file called "reaction_times.csv" in the TRiBot app data directory (it'll say were it is exactly in the debug box).
  5. Upload that file and post it in this thread.
  6. Also post what activities you did, and the respective skill levels.

Instructions for playing RuneScape:

  1. You can either mine rocks (no essence), or cut trees.
  2. Once you click a tree or rock, the debug will print "Object hash: 104343254," where 104343254 is a number greater than 0. If the number is equal to -1, that means the click did not register, and you should re-click the tree/rock.
  3. After you click, try not to make a bunch of mouse movements while waiting. Either keep the mouse fairly still, or move it off screen (if you want). You don't have to keep the mouse super still while it's over the RS client, but you should avoid excessive mouse movements because excessive mouse movements may result in inaccurate reaction timing.
  4. Continue doing this until you don't want to anymore.

Note:

  1. This is not a race. Do not aim for having the lowest reaction time possible. Please relax and play as you normally do in order to ensure reliable data.
  2. Do not left click on anything after the initial object click.

 

Thanks,

TRiLeZ

  • Like 14

Share this post


Link to post
Share on other sites

Will this get implemented into our client or whatever like human mouse? This seems MUCH less tedious hahah.

 

btw uploading my human mouse soon (:

uploaded^

Uploaded where?

 

So, shall i press  Z when i cut a log, or when the tree gets cut down?

When the tree gets cut down.

Share this post


Link to post
Share on other sites

@TRiLeZ , here you go boss , i started at 27 minning irons and played for an hour while pressing z here and there after it mined ,i stopped the script at 35 mining.

 

also may i please get my extended vip for completing all 22 data for the human mouse? thank you very much i hope this makes botting better for all of us!

reaction_times.csv

Share this post


Link to post
Share on other sites

I've updated the script. Users no longer have to press 'z' after the tree has fallen/after the rock has been mined. Just play normally and the script will collect data.

 

Could I get everyone who has already submitted data to submit some more data? I've made the script collect different kinds of data.

  • Like 2

Share this post


Link to post
Share on other sites

@TRiLeZ This is roughly 70mins - 76mins of data. I cut logs and oak logs for the whole time. I started the first half hour at Camelot cutting just oaks and trees and banking. The remainder I cut mostly logs then a smaller amount of oaks in lumbridge, while dropping when inventory was full.

 

My total xp gained was 18,250 and I was level 1 and now have 33 Woodcutting. All performed with iron then steel axe. (if all that detail matters lol)

reaction_times.csv

Edited by J M C

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • 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.

×