New Finding: Grand Phoenix is above Myth-Eye

[huchamabacha]

This will be my first new finding that isn't from a screenshot of already manifested talents, so someone please let me know if there's anything I need to fix/add!

I hatched a 1st-gen Emberstone Tiger (Duke Sierra) with a 1st-gen Marshfellow (Phoebe), and got the below result. I am using version 8.4.0 of the workbook with over-the-air updates. The last new finding row is 664.



I also tried to work out some of the logic to see if I understood the results the genome calculator was giving me. There's probably a more concise way to do this, but I think this makes sense, at least.

Fire sniper (Ultra-rare) is above all the Uncommon talents in both parents; since the only Ultra-rare talents in the offspring are below an uncommon talent, the two Ultra-rare talents of the offspring must be Fire Dealer and Myth Dealer.

Cheeky is above Fire dealer, so the lowest Common talent on the offspring must be Myth Eye.

Fire Dealer is below Ace Avenger and Critical Striker, so the lowest Epic talent of the offspring must be Grand Phoenix or Armor Breaker. However, Myth Eye is ranked above Armor Breaker, so this Epic talent must be Grand Phoenix.

So, Grand Phoenix must be ranked above Myth-Eye.

5Grand Phoenix

1Myth Eye

@Milt

[Milt]

Well yippee-ki-yay, we got a match!



I'm super relieved the verification system is working as intended. I didn't have any beta testers to call upon throughout this feature's development, so I had been concerned about unexpected misalignments in verification codes. Now that I've got the confirmation I was hoping for, I feel confident in calling the calculator a reliable peer-reviewing tool.

Your logic also checks out. Good job there!

For future reference, screenshots of the offspring's genome should still be provided to mitigate the risks of input errors in the calculator. It can happen to anyone, including me. But personally, I trust your word, so consider it approved.

I'll update the databases in a few . Thanks again for your valuable contribution!

[Milt]

Now that we've managed to add a couple more "new" talents into our databases, I'd like to take this opportunity to demonstrate to all contributors precisely why the last row parameter is super critical.



Whereas the verification code for this particular finding was 899 a few days ago, performing the same calculation backed by today's database (Jan. 14, 2021) instead yields a verification code of 898. I wasn't kidding when I stated how sensitive our verification algorithm can be. Setting the last row setting to 664 and running a database update immediately thereafter will thankfully yield 899 once more.

And to think this setting was a last-minute addition to 8.4.0...

Hope you all found this little sidenote informative .