May 19, 20214 yr getMouse().moveOutsideScreen()? snaps to the top-left corner of the screen after every moveOutsideScreen() call, so it enters the screen again from the same position, isn't this detectable?
May 19, 20214 yr 1 hour ago, Gam said: getMouse().moveOutsideScreen()? snaps to the top-left corner of the screen after every moveOutsideScreen() call, so it enters the screen again from the same position, isn't this detectable? It doesn't snap to the left top, whenever a mouse it out of the screen the position is -1,-1, that's why it's "visible" there Edited May 19, 20214 yr by Khaleesi
May 19, 20214 yr Author 14 minutes ago, Khaleesi said: It doesn't snap to the left top, whenever a mouse it out of the screen the position is -1,-1, that's why it's "visible" there Right, but doesn't that mean the starting point of the mouse when doing an action will be -1, -1 every time, when it previously executed moveOutsideScreen() which creates a pattern?
May 19, 20214 yr Client-side there is a packet which involves client focus too, so being alt-tabbed will have an effect. Unless they removed this in the super recent versions I'm sure it's still there. As for mouse's origin being -1 -1 don't worry about this it'll be different each time, with osbot you're in good hands. Using mouseOutside with a couple other mouse tricks (can't reveal any secrets publicly) would make it even better. Just try not to force the mouse to same coordinates each time.
Create an account or sign in to comment