Welcome!

Thanks. Any reason not to just always use concurrentlyTurnTo?

No worries, I appreciate it either way. The problem is the delay is pointless if it stops the login process. I don't want onLoop to execute before the player is logged in.

I'm not sure if we're talking about the same thing, but it definitely isn't removed. If you don't touch the camera and play for an hour, I can guarantee that the position of your camera is different. Why do you think the orientation of the minimap never matches the orientation of the camera?

Rambo501 submitted a new resource: Rambo Fisher - Fishes Fish Read more about this resource...

First of all there's not really much you can do with a macro recorder since the camera automatically moves over time. Anyway, mouse movements are being tracked and executing the same mouse movements over and over will get you banned. So I cannot imagine a mouse recorder would work very well...

What's the difference between the two? The API says it turns the camera "within a reasonable tolerance", what exactly does this mean? Is it less precise so more humanlike?

This works perfectly, thanks. Just wondering, am I doing something unusual here? If this is the janky way, is there any "proper" way to do it? Also, I just realized Execution.delayUntil also delays the log in process. So basically delaying until the player is logged in will delay forever, since...

Just tried, didn't work. Players.getLocal() is not null in lobby screen.

I'm not sure if this is supposed to be the case but Runescape.isLoggedIn() returns true in the "lobby screen" (not sure how this screen is called before you get into the game). This messes up my bot since onLoop starts executing before the character is ready. What's the proper way to check...