Jump to content
TRiLeZ

Human Mouse Implementation

Recommended Posts

How do i disable this? I'm getting 50% less profit...

 

 

Great update :D I find my bots run slower but idc tbh, i only care about ban rates

Understandable. People recording these 3 hour bits probably aren't as "efficient". I can't imagine 3hours of complete efficiency. I always slough off periodically, go get drinks, bathroom, etc.

 

But if you submit your own mouse recordings, I bet you could get efficiency. Just do one 3-hour efficient set of mouse recordings and your bots will surely follow suit.

Edited by boatsb4hose

Share this post


Link to post
Share on other sites

The mouse movements are slower but they're so much more human-like. Really loving it even with the decrease in profit which will easily be made up for the lower chance of receiving a ban xD.

 

EDIT: Realized there's an increase in CPU usage as well. Wouldn't hurt to make this an optional feature.

Edited by AsianNinja

Share this post


Link to post
Share on other sites

This uses alot of CPU. Normally my clients are anywhere from 15-25% depending on the script. When the was implemented I was getting over 50-60% each client so I could only run a few accounts. I found out how to disable it for the time-being until the cpu issue is fixed.

Share this post


Link to post
Share on other sites

This uses alot of CPU. Normally my clients are anywhere from 15-25% depending on the script. When the was implemented I was getting over 50-60% each client so I could only run a few accounts. I found out how to disable it for the time-being until the cpu issue is fixed.

Really? How do you disable it?

Share this post


Link to post
Share on other sites

An hour ago I found a very small bug with the Human Mouse, which resulted in the mouse movement/path generation to be tens of thousands of times less efficient than it should be.

 

I will release a patch later today.

Thank you so much TRiLez! Just to clarify, will this increase CPU efficiency, or just the efficiency of the mouse movements themselves (increasing in-game XP rates etc)?

Share this post


Link to post
Share on other sites

Thank you so much TRiLez! Just to clarify, will this increase CPU efficiency, or just the efficiency of the mouse movements themselves (increasing in-game XP rates etc)?

 

CPU/RAM efficiency. Maybe also the XP rate in case the inefficiency was causing the script to slow down.

  • Like 1

Share this post


Link to post
Share on other sites

CPU/RAM efficiency. Maybe also the XP rate in case the inefficiency was causing the script to slow down.

In your topic, you said "we can avoid detection to the extent by which Jagex uses mouse data in the detection process." how much of the detection process do you think jagex relies on mouse data? Like I would guess 95%, but what do I know. The rest would be log time and what else would u guess

Edited by boatsb4hose

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 update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 24 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.

×