Atrius97
-
Posts
291 -
Joined
-
Last visited
-
Days Won
34
Content Type
Profiles
Pokédex
Portal
Technical Documentation
Pages
Tutorials
Forums
Events
Downloads
Gallery
Blogs
Everything posted by Atrius97
-
Source: https://www.serebii.net/games/shiny.shtml
-
Yup, their legality checks and "transfer/trade" whitelisting system have never been consistent, regardless of which generation of games you're looking at. It's surprising we haven't found more issues with it, considering the sheer number of encounters/events they have to keep track of, going back nearly 2 decades.
-
This isn't a new issue either. Several past events were/are subject to this as well. Shiny Solgaleo and Lunala, (and several other HOME exclusives), were unable to trade in SWSH when HOME was first released, they were added to the trade whitelist at a later date. Shiny Jirachi from Channel/Colo Bonus Disc in Gen 3 were also barred from transfer until the first Tanabata Shiny Jirachi event, years later. Some events are still barred from transfer in other generations, such as the Odd Egg Pokémon from Virtual Console Crystal. (Odd Egg Pokémon must have the event move "Dizzy Punch" removed from them to be allowed past the whitelist, Nintendo has completely forgotten about that event to this day.)
-
This bug still continues to occur in newer versions of PKHeX as of 14/06/2020, in both Stable and Experimental Builds of PKHeX, I've opened a Github issue here reporting it: https://github.com/kwsch/PKHeX/issues/2859 Edit: Fixed here: https://github.com/kwsch/PKHeX/commit/8936c584173aacedbaac1734355a1eb2996d736e Thank you Kurt
-
I'm having an issue with the latest version of PKHeX, (v200314 as of writing) Holding Shift while sorting to mass sort all boxes seems to unintentionally change a number of Trainer Data values, drastically increasing the values: egg_hatching, capture_wild, total_capture, trade, and wild_pokemon_encountered. I believe PKHeX is somehow treating sorting the boxes as brand new encounters (pokemon caught/encountered values) and also trades simultaneously, as I have performed no trades on this savefile, yet the "trades" value reached into the thousands after sorting a few times. Update, 18/03/2020: It appears that virtually any use of the Batch Editor to modify Pokemon also triggers this issue.
-
This encounter actually can be reached directly after the Gladion Battle at the base of Mount Lanakila. The Rainbow Rocket arc does not need to be completed for this.
