Jump to content
TRiLeZ

Human Mouse Project [Data Collection]

Recommended Posts

Hello community,

 

I have started working on a new project aimed at making TRiBot's mouse movements as human-like as possible. To do this, I plan to implement real mouse movement data, replacing TRiBot's pseudo mouse movements.

 

Real mouse movement data will be generated by users, clicking strategically placed circles, all with different sizes. The data recorded will be movement locations and timings. After enough data is collected, I will work on analyzing the data and implementing it in the client.

 

That's right, TRiBot's mouse will use real, human mouse movements. We will be able to further throw off Jagex's detection systems, especially because Fitt's Law will be used along with the human mouse movements.

 

We are currently in the data collection stage, where I need the community's help. The details for providing help are listed below.

 

What will you be doing?

  • You will need to run a certain script. The objective will be to click ~628 red circles, which will take approx. eight minutes. After finishing, a file will be generated. You must upload the file in an attachment in a post in this thread.

When should this be done?

  • The sooner the better.

Will you receive compensation?

  • After you submit the required amount of files, you'll be given access to bot using the Human-Based Mouse (with your collected data). This will make all of your bots seem more human-like.

How many data files are needed per user?

  • I need between 20 and 22 data files per user. The higher, the more human-like the mouse will be.

 

Instructions:

  1. Open TRiBot's Mouse Data Collector tool via "File > Mouse Data Collector"
  2. Read/do:
    1. You will be clicking the solid red circles, one after another.
    2. Your goal is to click each circle quickly, and to only click once per circle (try not to misclick). Your clicks need to be as accurate as possible.
    3. If you can, set your mouse's reporting rate to the maximum.
    4. Set the client delay to the lowest.
    5. Do all of the clicks on one sitting. Do not do anything else other than clicking those circles for all of the ~628 circles. This will take approx. eight minutes.
    6. Post all of the data files under a single TRiBot account. If you use multiple TRiBot accounts to post the data, your data will be ignored.
    7. Do not post the same data files twice. I can tell if you do so.
  3. After clicking all of the circles, a file will be created, and the location will be stated in the debug box. Upload that file to a post in this thread.

The system to integrate human mouse movements is complete. All we need now is mouse data.

 

Thank-you,

TRiLeZ

  • Like 45

Share this post


Link to post
Share on other sites

Wow amazing, i think the mouse movement is indeed a very important step towards throwing of Jagex detection system! There are fjew scripters on this forum which make the mouse randomly move after doing certain things and i've been getting alot less banns from those scripts! I'll upload my files soon!

  • Like 3

Share this post


Link to post
Share on other sites

@TRiLeZ Well, it took me around 12 minutes

 

I'll upload my data shortly

 

but i do have two questions.

 

I noticed while i was clicking that my bot mouse was moving around(the little red x) moved around like three times when i was around 8 minutes through..(all it did was move, not click)

 

that shouldn't affect anything right?

 

Also, i found this interesting that while running the script clicking didn't disturb what i was doing. Does this mean that you could possibly play snake(or other games)/just adding overlays in general over the client without effecting your bot?

 

 

 

Edit 2: Unless you say otherwise im just going to add all the data on this post

 

Edit 3: Second Mouse Data

mouse_data-135006-1408007544516.dat

mouse_data-135006-1408011529180.dat

Edited by adamhackz

Share this post


Link to post
Share on other sites

@TRiLeZ Well, it took me around 12 minutes

 

I'll upload my data shortly

 

but i do have two questions.

 

I noticed while i was clicking that my bot mouse was moving around(the little red x) moved around like three times when i was around 8 minutes through..(all it did was move, not click)

 

that shouldn't affect anything right?

 

Also, i found this interesting that while running the script clicking didn't disturb what i was doing. Does this mean that you could possibly play snake(or other games)/just adding overlays in general over the client without effecting your bot?

1. If that happened only three times, then you//your data should be fine.

2. Yes, it's possible to add overlays and to block input made on them via the script (EventBlockingOverride).

Share this post


Link to post
Share on other sites

@TRiLeZ How many of these are you planning on evaluating? Thanks for the constant improvements, since the ABC and the requirement for scripters to use the methods I've been banned much less with premium scripts.

 

I also went ahead and did 7 of these incase I'm eligible for compensation voucher. :) I don't think any of my recordings are less than 8:50 lol..

mouse_data-64706-1408066502462.dat

mouse_data-64706-1408068460523.dat

mouse_data-64706-1408069025048.dat

mouse_data-64706-1408069559811.dat

mouse_data-64706-1408070993042.dat

mouse_data-64706-1408071530991.dat

mouse_data-64706-1408072070587.dat

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
      • 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
      • 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
      • 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.
      • 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!
      • 30 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×