You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I'm doing a nuzlocke of an X Randomizer I built a few days ago, and one of the things I randomized was Gift Pokemon. The Lucario you battle Successor Korrina with is one of the Pokemon that can be edited, and was randomized into a Roggenrola with Lucarionite.
Sounds normal so far, right? I thought the same until I actually got through the battle. Regardless of if I win or lose, after the battle, Korrina suggests that Lucario "gets the chance to Mega Evolve" in battle and rematches me, yet it's basically impossible for me to Mega Evolve a Roggenrola.
I learned this the hard way lmao, so there could be two possible fixes for this:
Have the randomizer change everything EXCEPT for Lucario
Randomize everything, but change Lucario into another Pokemon that can Mega Evolve, as well as the Lucarionite into the randomized Pokemon's appropriate Mega Stone (e.g. Lucario is randomized into Venusaur, Lucarionite is then changed to Venusaurite)
The text was updated successfully, but these errors were encountered:
Just to clarify, changing Lucario with Lucarionite to Venusaur with Venusaurite DID indeed work. All the game does is check if your Pokemon in the battle Mega Evolved, doesn't matter if it was Lucario or not.
So I'm doing a nuzlocke of an X Randomizer I built a few days ago, and one of the things I randomized was Gift Pokemon. The Lucario you battle Successor Korrina with is one of the Pokemon that can be edited, and was randomized into a Roggenrola with Lucarionite.
Sounds normal so far, right? I thought the same until I actually got through the battle. Regardless of if I win or lose, after the battle, Korrina suggests that Lucario "gets the chance to Mega Evolve" in battle and rematches me, yet it's basically impossible for me to Mega Evolve a Roggenrola.
I learned this the hard way lmao, so there could be two possible fixes for this:
The text was updated successfully, but these errors were encountered: