Skip to content
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

automaps and autofight often stopping working, #185

Open
jus7aguy opened this issue Apr 3, 2019 · 6 comments
Open

automaps and autofight often stopping working, #185

jus7aguy opened this issue Apr 3, 2019 · 6 comments

Comments

@jus7aguy
Copy link

jus7aguy commented Apr 3, 2019

Last week in chrome auto-maps and autofight have both stopped working regularly. It's occasionally been fixed by reloading and re-starting the script. But not always.

@dogdutch
Copy link

dogdutch commented Apr 7, 2019

I'm having the same problem. It freezes on the maps screen and reloading solves this until the program triggers maps again where it will freeze again.

@jus7aguy
Copy link
Author

jus7aguy commented Apr 7, 2019

I found a temporary work around, disable heirloom management. I think something in the new "core" heirloom is messing it up.

@dogdutch
Copy link

dogdutch commented Apr 7, 2019

I'll give it a shot, thanks for the tip!

@dogdutch
Copy link

Can report have not had any issues since doing this, great catch!

@Zak-Michael-Armstrong
Copy link

I've also been experiencing this the last few days. Seems to trigger upon completing spire 1, which would be consistent with the new "core" causing an issue.

@Zak-Michael-Armstrong
Copy link

Can also confirm that disabling heirloom management appears to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants