Atrius97

You didn't follow the tutorial properly. Your PID has to match the correct Method for the type of encounter (in this case Method 1), and you have to match the nature provided by that PID. For older games, PID and EC are the same, so copy the PID to the Encryption Constant as well.

Use the Encounter Database under Tools > Data to select an Alpha encounter. There are multiple values you need to correct to change a regular encounter into an Alpha encounter, it's easier simply to start with an Alpha template. It is not the same as the Gmax flag in SWSH where you can simply toggle it and it's automatically legal. The Alpha moveset, level, met level, Height, Weight, and Copy Height all have to be corrected.

See this tutorial for solving PID mismatch: The second error can be resolved by setting the Latest (not OT) Handler properly, as it's a transferred pokemon, you cannot be the original trainer.

Given how GameSync ID used to work for prior games, this is very likely the case. Unfortunately, we can't trust players would upload exclusively saves that had never been online before, and the Project Pokemon staff would be forced to verify each savefile individually. On the other side of that coin, exposing that value publicly to be edited/"removed from saves that had been online before" opens up an avenue for potential abuse/exploits that could cause TPCi to introduce additional telemetry and/or kick off another banwave.

They implemented this new verification into ACNH quite late. There is no reason they can't decide suddenly to implement it for LGPE, SWSH, or BDSP. There's a HOME compatibility update on the horizon, I don't expect them to suddenly upgrade verification for all 6 remaining game versions, but the chance isn't zero.

Not even game bans, the "ban" is lifted if you stop using the blacklisted savefile. The ban does not occur with official transfer methods, like local save transfer between two switches within the same Nintendo account. I would assume if the Nintendo account remains the same, their check clears, even if you moved it with JKSV or Checkpoint.

Due to reports of savefile verification and savefile being banned if they are used by more than one account/switch, we STRONGLY suggest you don't use publicly uploaded savefiles obtained outside Project Pokémon either. Importing/exporting individual Pokémon files is safe, and uploads of .pa8 files/collections of .pa8 files will be permitted on Project Pokémon, but full savefiles will not be permitted, as it poses a potential ban risk for all users of said publicly shared savefile.

If you only care about the TID, in PKHeX, simply hold ALT and Left Click on the star icon next to the PID. This will alter the Secret ID to be shiny without changing the Trainer ID or PID. If you want all pokemon to match the exact same Trainer ID AND Secret ID, then you will have to find new IVs/Nature/PID combinations that match your desired TID and SID combo. To do this, in Pokefinder, set up a profile with the desired Trainer ID and SID, go to Gen 4 and the correct option for the type of encounter, then Searcher, set the correct Method for your encounter, enter your desired filters and set Shiny to Star/Square, then hit Search.

There is a repository of "glitch mon" savefiles here: https://www.youtube.com/watch?v=zPiS2T5z-KQ https://sites.google.com/site/torchickens2/pokemon-save-files

At time of writing, while ban reports have significantly trickled off since earlier this year, we are still receiving the occasional ban report on the PPORG and PKHeX Development Discord servers, seemingly related to the HOME banwave in January. We've been able to track some of the reports to earlier offenses, such hosting hacked raids prior to the hacked raid banwave during early Isle of Armor, or ranked/tournament cheating. It seems that they audited server logs and cleaned up a few stragglers they had neglected to ban earlier, and tacked them onto the HOME banwave. Given that they've demonstrated that HOME can track and accurately ban users who used the methods that resulted in the banwave, just because the banwave appears to be "pretty much over, and I wasn't banned despite doing X or Y bannable action" doesn't mean they aren't continuing to monitor network traffic and banning anyone foolish enough to attempt trafficking illegal pokemon via HOME going forward. The HOME banwave is thought to be the result of a permanent, ongoing security feature, not a one-off wave. As well, they've also shown the ability to view and edit Pokemon stored on the savefile, (including those in Poke Jobs AND in both Daycares, sending them there doesn't "hide them from HOME"), as HOME was used to automatically fix movesets for Alolan Form GO-origin Pokemon that had their opposite regional form moveset due to a bug with GO -> HOME transfers. This means that any illegal pokemon, glitch pokemon, etc. may be viewed by HOME any time you load your savefile into HOME, even if you don't place them into HOME storage itself. If you kept any illegal/glitch Pokemon on your savefile, proceed with caution with that infomation in mind. (Alternatively simply avoid using HOME altogether, or store any illegal/glitch pokemon on a profile/savefile, secondary switch, or emuNAND that is not going to be accessed by HOME.)

Here are examples of the entrance animations, Top is Square (XOR=0), Bottom is Star (XOR=1-15) (Photos courtesy of Serebii.net: https://www.serebii.net/swordshield/shinypokemon.shtml)

Update, surprisingly: If you selected the OT name "ASH" from the default name menu instead of manually entering it, the savefile's OT trash bytes would apparently grab "ASH\0JACK\0". This meant that editing Pikachu would still be broken if you had that exact OT selected from the default name menu and edited Pikachu at all, as PKHeX would still clear some of those trash bytes. This has been resolved here: https://github.com/kwsch/PKHeX/commit/d41fc571d05dfa8c455f5cd25c0be338b0e0a3fa

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.