Jump to content
IceKontroI

Simulating off-screen activity with mouse

Recommended Posts

Generating antiban is important, and I'm interested in creating realistic antiban procedures that real players do. I know moving the mouse off-screen is something Tribot can do, but when you move the mouse off-screen with Mouse.leaveGame() it moves from point A to point B, but when it re-enters the screen it goes from point B again (the exit point) to point D. I want it to move from point A to point B, then re-enter the screen at a new point C to point D which is considerably more believable. Here's a visual if my words confuse you.

http://imgur.com/a/HANxM

Is there a way for Tribot to do this normally or will I have to manually code it in myself, and if I do are there are functions I need to be aware of? This is a small but important part of my script's antiban so I would really like to make sure it's optimized.

EDIT: I've even tried using Mouse.leaveGame(true) and it doesn't drag the mouse back in from a different point than the one it exited from so that doesn't seem to be the answer. It does, however seem to be a good choice since it makes the game client think it's not the window in focus any more.

Edited by IceKontroI
  • Like 1

Share this post


Link to post
Share on other sites
13 hours ago, IceKontroI said:

Generating antiban is important, and I'm interested in creating realistic antiban procedures that real players do. I know moving the mouse off-screen is something Tribot can do, but when you move the mouse off-screen with Mouse.leaveGame() it moves from point A to point B, but then it goes from point B (which makes it look like you didn't really move the mouse off-screen) to point D. I want it to move from point A to point B, then from point C (to show you are going from one window to another) to point D which is considerably more believable. Here's a visual if my words confuse you.

http://imgur.com/a/HANxM

Is there a way for Tribot to do this normally or will I have to manually code it in myself? This is a small but important part of my script's antiban so I would really like to make sure it's optimized.

NOTE: I've tried using Mouse.leaveGame(true) and it doesn't drag the mouse back in from a different point than the one it exited from so that doesn't seem to be the answer.

I think this would be a much more believable mouse movement pattern. You mouse would never return straight from where it left.

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 key event handling issue


      Fix other event handling issue


      Fix RSServer hook


      Update world hopper to have it use OCR, thanks to Todd


      Use proper disposal of old Graphics objects


      Reformat code


      Rearrange code


      Organize code imports


      Apply around 8000 automated code refactorings


      Make preparations for Java 9


      Fix 11 various bugs


      Add more reliable debugging support


      Fix mouseEntered/Exited event dispatching bug


      Fix minimap walking bug where it opens the map


      Fix broken hooks for today's game update
      • 46 replies
    • This update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
      • 27 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
      • 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.
      • 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
      • 22 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×