You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch
Describe the bug
Currently the mouse is not registering in the client with the code System.out.println(((Applet) bot.getClient()).getMousePosition(true));
This returns null if the actual cursor is outside the client.
This would absolutely result in bans.
To Reproduce
Steps to reproduce the behavior:
Insert the line of code after mouse moves
Launch client and observe the mouse move reports and the nulls.
Expected behavior
The nulls shouldn't exist. Our actual mouse is being tracked and this is an issue. Clearly this needs to be looked into.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
GigiaJ
added
critical
urgent or causing complete failure in entire program (crashing or looping)
bug
Denotes that this a bug
imperative
imperitive, needs to be done immediately
labels
Oct 17, 2020
Possibly convert the actual canvas file into one we want?
Instrumentation?
GigiaJ
added
major
very important or causing major difficulties or failure with a feature(odd or poor performance)
and removed
critical
urgent or causing complete failure in entire program (crashing or looping)
imperative
imperitive, needs to be done immediately
labels
Jan 31, 2022
BEFORE REPORTING
Ensure RuneLite is up to date in IDE and you are using the latest version of the master branch
Describe the bug
Currently the mouse is not registering in the client with the code
System.out.println(((Applet) bot.getClient()).getMousePosition(true));
This returns null if the actual cursor is outside the client.
This would absolutely result in bans.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The nulls shouldn't exist. Our actual mouse is being tracked and this is an issue. Clearly this needs to be looked into.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: