Molly
Members
-
Joined
-
Last visited
Everything posted by Molly
-
-
-
-
Another user was having similar issues. The following resolved the problems for him. 1) Start a fresh Runescape client - do NOT login to the game. 2) Start OSBot in mirror mode. 3) After OSBot has attached itself to the Runescape client start the script.
-
-
-
-
-
-
-
-
-
Oh yeah you can for sure make it better than the barebones example I gave, was just trying to illustrate the point that this isn’t something without a solution that’s impossible to figure out.
-
I'm not sure it's fair to say nobody knows how to fix this. A straightforward solution would be to record a couple thousand mouse paths of varying distances and base your script's mouse movements off these. Example: I need to move my mouse 70 pixels, I grab from my thousands of human mouse paths some that are around 70 pixels, say between 40-100. I grab one of those paths, stretch it or shrink it, add some noise to it and use that path to move the mouse. The downside to this is it requires a fair amount of work recording that many mouse paths and realistically is easier to do and probably better for not being "detected" if done by each scripter individually for their own scripts.
-
I think the important thing to take away here is that they do at least send the mouse data to their servers, it doesn't look very human, and if they wanted to they could use this as one of many metrics to detect bots. That alone should be enough to encourage a change, whether it be in the way OSBot itself handles mouse movements or by us scripters to handle movement ourselves.
-
-
-
-
-
-
No problem, that's what I'm here for!
-
-
-
Sure, gave you one just now.
-
Before running the script again make sure to start a fresh client. If the bug still occurs please message me, or post here a copy of the logger. In the mean time I'll see if I can replicate the issue. I have not had it on start but perhaps I can get it to happen after some time. This should be fixed now.
