Closed daradux closed 7 years ago
According to the Megaten Wikia, these fusions with rare personas like Regent take the current level of your ingredient persona (Setanta in this case) instead of their base level, so the resulting persona differs depending on Setanta's current level.
It probably creates an Okuninushi if Setanta's current level is closer to its base level (28), but as you level it up it will be creating more powerful personas in the Emperor arcana (such as Barong, which is the next "rank" after Okuninushi).
I believe the calculator assumes that the ingredient persona's current level is its base level as well, but maybe @chinhodado could confirm here if I said something wrong. Just my 2 cents.
So... maybe try fusing a brand new Setanta at a lower level?
By the way, maybe a visual disclaimer next to fusions with the special treasure personas would be handy for the users of the app. I could contribute to that if needed.
@edmilsonrobson Thank you for your thorough explanation! That makes sense. My Setanta was way overleveled. The visual disclaimer you bring up sounds like a really good idea. I'm new to github and coding in general, but please let me know if there is any way I can contribute or help (i.e. testing things out).
Thanks again! 👍
The note for rare fusion is already there in the recipe section:
"Also, remember that rare persona fusion depends on your persona's current level."
@chinhodado Oh, I feel embarrassed now, I remember reading that around the time I started playing P5 and also started using the app, but not getting exactly what it meant. When this happened I forgot about the meaning of that note, and didn't connect the dots. My apologies for wasting your time!
I do like @edmilsonrobson's suggestion about making it a bit clearer with the visual disclaimer, but as @chinhodado stated it's already there - just me being stupid and not understanding what qualified as a rare persona.
Thanks again for developing this fantastic tool! Feel free to give me a digital slap or close this thread. (edit: Fixed some of the English and added a section about @edmilsonrobson's suggestion)
edit [My mistake, a non-issue, "solved" (in quotes since it was a non-issue) and explained by @edmilsonrobson and @chinhodado below. I'm so embarrassed now, sorry again guys, and thank you for your time!] old post below: