Zach
Developer
-
Joined
-
Last visited
-
Sure why not 😆 -
I did some research on the matter. Not sure there is a way to cleanly fix this without some hacky workaround. Thank Google Chrome developers for failing to adhere to standards...(or rather that they're distinguishing between autofill and autocomplete). Anyone have thoughts for a clean fix?
-
-
I just fixed some mirror issues. No redownload necessary, just re-run the bot and it should work.
-
It can take a while as it needs to download the game client from the RS server as we've stopped caching it.
-
Changelog: -UI Threading changes to correct some issues -Fixed some bugs
-
Do you remember what the problem was or if it was resolved? I didn't receive any other reports about it either.
-
I gradually and silently changed that; such that by end of Nov 2017 (and this is how it should be currently): -Message, config, login code listeners execute on a single "listeners" thread. This checks for changes approximately every 100ms. -Audio listeners execute directly on the game thread. Next few updates may see audio listeners also moved to that listeners thread mentioned above. We initially hesitated on this due to the potential response times required. But I think we can compensate by lowering the time between checks.
-
Fixed several more bugs. Restart bot and it should be live.
-
Patched several bugs related to the latest RS release. Edit: Aware of mirror bug with loading hooks. Will release a fix for it once scripters start to confirm that the changes have worked.
-
Issue should be fixed now.
-
Should be fixed now.
-
-
Fixed
-
Just to let you guys know, occasionally I will be reloading the chat for new features. So if you get disconnected, that's probably what happened. Refresh the page and you'll be good to go. I'll eventually get around to automatic reconnects, but I don't want to do it until more of the bugs are ironed out.
