Atrius97

If you are unwilling or unable to follow the guides, I suggest installing Autolegalitymod, so you don't have to return begging others to legalize things for you every time: https://github.com/architdate/PKHeX-Plugins/wiki/Installing-PKHeX-Plugins https://github.com/architdate/PKHeX-Plugins/wiki/Getting-Started-with-Auto-Legality-Mod

Make sure to have saved ingame twice and that it's been properly extracted via Checkpoint or JKSM/JKSV. https://projectpokemon.org/home/tutorials/save-editing/managing-3ds-saves/ If you are moving the savefile via FTP, also make sure your client is set to Binary mode, not ASCII, as ASCII will cause corruption.

No. Those Pokémon do not exist in the game ROM itself and cannot be added by PKHeX. Adding them to the game would require a full ROM hack to add the proper data for all missing species.

The issue with all three of these is related to PID Mismatch. See our guide for solving that here:

Dump the correct patches from your Switch, many Pokémon were not introduced into the game until the Isle of Armor and Crown Tundra update patches.

As a sidenote, this line on Bulbapedia makes me believe that even more data is stored by the Pokéwalker: https://bulbapedia.bulbagarden.net/wiki/Pokéwalker#Other_Pok.C3.A9walkers If this is to be believed, this would imply that the trainer data and entire party for the player is also stored by the Pokéwalker, because the game reconstructs a battleable version of the other player in the Trainer House. I suspect that would imply the Pokéwalker is capable of storing fully formed pkm data, rather than just partial pkm data, since it clearly can store an entire team of 6 from the player party.

The savefile must be a properly exported savefile. Savestates cannot be used with PKHeX, and some emulators may also produce files of the incorrect size or format. Moving files using FTP can also cause corruption if the FTP client is not set to Binary mode, as ASCII mode will alter the data.

Both of these errors are known issues. The Clefairy distribution dates have already been fixed in the PKHeX Development build, and will be resolved in the next stable release. Please only report issues if they can be reproduced in the most recent dev build, and you've made sure it's not user error. The Dracovish issue is with the wondercard itself, which contains an error. This issue is on GameFreak's end, not PKHeX's. You can resolve it by creating a folder named mgdb in the same directory as PKHeX.exe, and putting the "fixed" wc8 file in that folder. To my knowledge, this fixed wondercard will also be included in the next stable release.

If you absolutely must download that version, you're free to download the old commit and build it in Visual Studio yourself, release builds for very old legacy versions are not available. https://github.com/kwsch/PKHeX/releases/tag/19.07.05

I'm not sure if PKHeX has documented the date range for that event yet. It will be resolved later, just select a day on or after Sept 3rd 2022 and ignore the warning for now.

As far as I'm aware, this may already be resolved in the latest development build of PKHeX, can you check again using that build?

Please make sure to report errors only after trying to reproduce the issue on the latest development build: If the issue doesn't occur there, then it's already been resolved, and will appear fixed in the next release of PKHeX.

When a Ribbon is equipped, the Pokémon will display their title in every battle. Here's an example, the Espeon below has the Earth Ribbon (from Mt. Battle in Pokémon Colosseum or XD: Gale of Darkness) equipped, and the Noctowl has the National Ribbon, (Shadow Pokémon obtain this ribbon when purified).

In Pokemon Sword and Shield, you can equip a ribbon to grant a Pokemon a title when sent into battle. Each ribbon has a unique title associated with it, including Marks. That option is the currently "Affixed Ribbon". https://bulbapedia.bulbagarden.net/wiki/Title

Local transfers are only permitted between the same Nintendo account, to my knowledge.

You don't need two copies of the game. You can do local savefile transfer between two consoles (this is not the same thing as Cloud Saves, do not use Cloud Saves with edited savefiles.) Also, if the custom firmware switch does not have anything bannable installed, it can safely go online in Sysnand CFW, so the second console is unnecessary if your reason for having a second untouched switch is so you have "one that can go online."

Your switch has to have custom firmware to extract the save file in the first place, no one can inject that into your game for you without the save file. Those items cannot be traded, and even if they could be, it wouldn't activate the event for your save.

If you have Sword/Shield, you can rename pokemon that didn't originate from your savefile, as long as they do not already have a nickname, are not a foreign language Pokémon, and are not a "fateful encounter". Transferring them to SWSH through HOME would allow you to select a new nickname at any Name Rater in any Pokémon Center, but be aware the change is permanent once given a nickname. If you have an older model switch, you can easily install custom firmware and extract your savefile, check this site to see if your switch is "unpatched" and can be modified. https://ismyswitchpatched.com/ If it is unpatched, proceed to this guide: https://nh-server.github.io/switch-guide/user_guide/sysnand/sd_preparation/ If you don't have a hacked switch/are unable to hack your switch (if it's patched, a V2, Lite, or OLED model), you can still use PKHeX with Gen 8 games without custom firmware. If you need something traded to you in Generation 8, consider going to the "#sysbot-servers" channel in the PKHeX Development Project server to find a server hosting an instance of the Sysbot.NET bot. https://discord.gg/tDMvSRv Sysbot.NET is capable of dumping your Pokémon to files, allowing you to alter them in PKHeX, and then trading them back to you. Be aware that you should trade the bot your original copy of your Pokémon for the altered copy, as having two copies of the same Pokémon in BDSP will potentially set off the "PokeDupeChecker" and cause them to become flagged as a clone, which will make them unusable online. (This only occurs for Pokémon that originate from BDSP, and are not natural clones like Nincada or NPC trade Pokémon)

For reference, you need custom firmware to extract your savefile from your 3DS. The savefiles found on the SD card by default are not usable in their current format, you can't just copy the file off the SD card and drop it into PKHeX, PKHeX won't be able to read it. If any of the data was lost or overwritten during the recovery process, it's unlikely the savefile will still work, but you can try to extract it using custom firmware and it may potentially load into PKHeX where some of the box and party data could be intact, in which case you would lose your progress, but you could save your Pokémon and transfer them to your new savefile.

Instructions and troubleshooting go in this thread ^

That's not entirely accurate, yes a copy of the Pokémon does remain on the HGSS savefile, but there is essentially a partial clone contained in the Pokewalker data itself. You can do a key combo at the Pokewalker menu in HGSS to "recall a Pokémon" if your Pokewalker is lost or broken, because the entire "original" Pokémon is still in a hidden slot on the savefile, but there is something on the Pokewalker more than just the species index value. If you test the Pokewalker using Spinda, you can see that the spot pattern is retained, as are form differences with gender and such for other species. Spinda having the correct spots is important, because that means the PID value is also retained by Pokewalker, as that is required to render accurate spot patterns. If one were to dump the RAM of the Pokewalker and recover that PID value, it could be used to reconstruct the Pokémon's Nature, Gender, IVs, etc. I'm unsure if Nickname, Trainer ID, Secret ID, Trainer Name, moves, level, etc. are also all retained, but the PID alone would be plenty to go off of. It looks like some other communities have done a significant amount of digging into Pokewalker hacking, like these two for example, they appear to have made some headway: http://dmitry.gr/?r=05.Projects&proj=28. pokewalker https://github.com/mamba2410/reverse-pokewalker It would take some significant effort and some digging to find it, but it's in there... Somewhere.

There is no bug. The National Dex is required before proceeding into those areas.

In general, most pokemon will not get you banned, especially if they have legal values. To my knowledge, they've only been three ban waves during Gen 8, hacked raids prior to Isle of armor, the HOME ban wave in January 2021 (people were moving obviously hacked Pokemon through HOME, via account sharing) and a few isolated Korean bans from a tournament where they were using Pokemon that were obviously hacked, to the point that they included nicknames of websites that sold hacked Pokemon. It's also perfectly fine to transfer save files locally between two switches, although Cloud saves should be avoided if the save was altered in any way.

Have you saved ingame twice? A battery file isn't generated unless you actually save using the ingame menu. Savestates do not count.

Also, please do not double post. If you don't obtain an answer right away, wait. Don't make an identical post because your first one hasn't been answered yet.