Everything posted by Zach
-
[Stable Build] OSBot 2.3.123
- [Stable Build] OSBot 2.3.123
Interaction/Mouse updates Bank supports NPCs/closed chests/GE. Other misc fixes. Couple of internal changes to lay the groundwork for some new changes coming up- Session has expired due to inactivity or multiple bots. HELP PLEASE.
Try it one more time for me please I just tried a couple of things- Session has expired due to inactivity or multiple bots. HELP PLEASE.
Usually this is because there is a background bot process that hasn't shut down completely. Other times the error can occur is after you've put your computer to sleep or other conditions where it's disconnected from the server for at least an hour. Then when it tries to reconnect, the server no longer has that as a valid session, so it blocks the connection.- apparently bot is down
If you guys were wondering, the bot was updated 40 minutes ago and should have been working since that time.- Proxy Setup [Purchase --> Client Configuration]
The reason why proxies don't work in Mirror is because we don't control the loading of the game. The loading is handled by Jagex's official client or whatever you're using to load RS. So, when those programs support proxies, it will be usable. We have no control over that situation.- Bot client stuck loading after login
I haven't had this happen to me before. Does it happen every time or only during certain times? Do mouse clicks or keyboard events (mash on your keyboard a bit) go through to the game? What are you using to load the game? For example, Firefox.- [Stable Build] 2.3.120-122
.122 out as outlined in the first post.- Scripts dont start in 2.3.120
Looks like that script was trying to do something outside of the API, but doesn't look like an issue from our end. I'll take a look if you PM it to me. Otherwise, I would contact the script writer.- [Stable Build] 2.3.120-122
Real distance cannot be calculated if the object is unreachable. So, the object must be reachable.- Scripts dont start in 2.3.120
- [Stable Build] 2.3.120-122
Call closest(false, ...) Edit: For anyone else that's wondering, closest(false, ...) is the original behavior for closest(...). In this update, closest(...) was changed to closest(true, ...).- [Stable Build] 2.3.120-122
.121 patches AutoLogin handler.- Mirror client bug report - positions
We've been talking about a solution to this. I haven't forgotten about this bug in my bug fixing festivities.- [Stable Build] 2.3.120-122
Yea it's better. Edit: .120-.121: Apparently that's not good enough for a release thread, so I'll include some info: EntityAPI.closest uses real distance instead of pythagorean. Real distance cannot be calculated if an object is not reachable. If you need to restore original behavior, use closest(false, ...) Mouse event changes to be more accurate. Couple internal changes, including some to reduce CPU usage. .122: Reverses the EntityAPI.closest() changes. Now closest(...) has the same behavior as closest(false, ...)- MirrorClient v1.102
Correct. Make sure you have RS loaded on the browser or somewhere.- MirrorClient v1.102
It's automatically updated with the bot client. There is no need to download anything else.- [Stable Build] 2.3.117 - Interactions, Break Manager update, patches
They work fine.- MirrorClient v1.102
- MirrorClient v1.099-1.101
It's automatically updated with the client now.- [Stable Build] OSBot 2.3.114 - Camera Zoom
Mirror should be working now. Just restart your bot.- [Stable Build] OSBot 2.3.114 - Camera Zoom
That's for mirror right? I'll work on fixing it.- [Stable Build] OSBot 2.3.114 - Camera Zoom
Fixed an issue that was preventing it from running scripts. Restart your bot and it should work.- MirrorClient v1.096-1.098
It's integrated with the bot now.- [Stable Build] OSBot 2.3.97/98
Camera changes. Some core changes. Some more changes to lay the groundwork for more of the web walking changes. tl;dr Changes. OSBot 2.3.98 @Alek -Chatbox isVisible() checks -ResizableMode update -Modeled getHeight() update - [Stable Build] OSBot 2.3.123