-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling automatic safari zone disables the RTC and other enabled auto* scripts and does not function #364
Comments
Yup, same issue here - auto clicker seems to work for a very short time but I need to re-click to start it again. Disabling the Safari script gets everything working once more. |
@lnlyssg The autosafari script has already been updated to fix the problem (and this issue should get closed). Please check whether you’re using the latest version and if so make a new issue with error logs. |
Hi, can confirm this issue is still taking place with the latest version (v.0.10.17) and the update installed, at least on the desktop client - enabling the auto safari doesn't disable all the other scripts for me, but it doesn't actually load the auto safari options. (Confirmed as of 12.01.2024 to be an open issue.) |
Bit late coming back to this but I ran the Script Fixer Upper which seemed to get everything working again (was definitely on the latest versions) |
Thanks for the suggestion, ran that and it now works perfectly again, thanks for the help! |
Hasn't fixed the other issue with the autoclicker, but at least the autosafari works again |
For some reason if I enabled the autosafarizone script any other auto scripts(like autohatchery or automine or simpleautofarmer) stop functioning as a whole, alongside any time-based items within the game(like automatic wild Pokemon battles, dungeon timers, harvest timers, battle item timers etc)
On top of this, the autosafarizone script even when enabled by itself does not currently seem to function at all. Specifically, none of its toggles seem to appear to even use it.
The text was updated successfully, but these errors were encountered: