We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This only happens when the evolution is synced through PADListener. If the evolution is manually updated on PADherder, the expected behavior occurs.
Expected behavior: After a monster reaches the target ult evo, the "next evolution" step should be "None".
Actual behavior: Instead of "None", the next step shown is a devolution, resulting in incorrect evo mat requirements/reminders listed in PADherder.
The text was updated successfully, but these errors were encountered:
I can confirm this with my Shiva.
Sorry, something went wrong.
689438c
No branches or pull requests
This only happens when the evolution is synced through PADListener. If the evolution is manually updated on PADherder, the expected behavior occurs.
Expected behavior: After a monster reaches the target ult evo, the "next evolution" step should be "None".
Actual behavior: Instead of "None", the next step shown is a devolution, resulting in incorrect evo mat requirements/reminders listed in PADherder.
The text was updated successfully, but these errors were encountered: