[Port] ABCUtil#leaveGame is extremely predictable - HUGE oversights on 'anti-ban'
Original Author: Worthy
Description of the bug (be specific): Calling the ABC2 Leave mouse command, the mouse only leaves the game to the top of the screen. No matter where the mouse is on the screen, it ALWAYS goes to the top. Normal players leave the game to browse all sorts of windows in any direction, but the TRiBot method only moves to the top of the game window (and which people have windows ABOVE the TRiBot client window).
FURTHERMORE: Say our mouse is IN-GAME at point A. It moves off screen (and remains at the edge of the screen) - let's call this point B. Once the mouse moves BACK INTO the game it goes from point B to a random point C. This is quite indicative of bot-like behavior as no player re-enters the game from where they went to click on another window from the exact same point they left the window.
How often the bug occurs: Every time Triggers of the bug (if known): Calling ABCUtil#leaveGame() Java Version: 1.8.0_91 64bit Max Heap Size: 386MB TRiBot client version: TRiBot Release 9.303_6 Looking Glass (yes/no): No Operating System: Windows 10 Script Name: N/A TRiBot Old-School or RS3: 07 Client Debug: N/A Bot Debug: N/A
Example: This is the script I used to test:
Output: [23:31:03] Moved mouse to 618, 109 [23:31:07] Left game to 577, -8 [23:31:17] Moved mouse to 202, -1 [23:31:21] Left game to 224, -9 [23:31:23] Moved mouse to 242, 191 [23:31:29] Left game to 316, -2 [23:31:31] Moved mouse to 332, 130 [23:31:36] Left game to 279, -2 [23:31:38] Moved mouse to 568, 518 [23:31:43] Left game to 619, -3 [23:33:39] Moved mouse to 322, -5 [23:33:43] Left game to 148, -2 [23:33:45] Moved mouse to 155, 375 [23:33:49] Left game to 238, -2 [23:33:51] Moved mouse to 238, -2 [23:33:55] Left game to 383, -13 As you can see, the y coordinate is always negative once the mouse leaves the game. If you run the code I have provided above you will see that this is because the mouse only exits to the top of the screen.