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

Problem in Kirin evolution chain #776

chayashida opened this Issue Oct 16, 2015 · 4 comments


None yet
4 participants
Copy link

chayashida commented Oct 16, 2015


I noticed there was a problem evolving #1218 Kirin of the Sacred Gleam [L/L].
#2077 Green Gleaming Star Kirin, Sakuya [L/G] isn't available from her drop-down menu.

Also, when trying to set up the Evo for #751 Incarnation of Kirin, Sakuya to be #2077, the following error message is displayed on the dialog box to the left of the Cancel button:

Error: 400 {"target_evolution": ["Invalid target_evolution for this monster"]}

Let me know if you need more information. (I already has a workaround for the problem by deleting and re-adding the monster).

Thanks for a great site!


This comment has been minimized.

Copy link

madcowfred commented Oct 16, 2015

Yeah, I know something is very screwy with Kirin. I hope to have some time to look into it this weekend :(


This comment has been minimized.

Copy link

iNeedMoreAccounts commented Nov 18, 2015

Kirin's evolution chain isn't like most monsters. The base form (751) evolves into #752. Then #752 can branch into #1218 or #2389. #1218 can further evolve into #2077.

I just changed my Green Star Kirin (#2077) to the new Awoken Sakuya (#2389) and I had to reverse evolve it twice. I can't recall ever having to do that for any monster ever since I started playing pad. I think with most monsters all three 'ultimate evolutions' would branch from #752.


This comment has been minimized.

Copy link

theinfra commented Dec 31, 2015

Bump, this issue is stil happening.

I know it's been weeks since last activity here and since September with the latest new article, but this is a great tool that sadly needs a lot of fiddling to keep up to date or else it's gonna fall into obscurity :C

@madcowfred madcowfred closed this Jan 1, 2016


This comment has been minimized.

Copy link

madcowfred commented Jan 1, 2016

I've reworked how evolutions are verified in the API, it now just does a basic graph traversal check to see if the target is reachable from the monster. The old method for finding an evolution chain scares me and is the most fragile part of the code, I hate having to touch it :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment