theSLAYER

RoC's PC should have all the gigantamax mons, as well as mons caught in SWSH. Rather than create mons from scratch, it'll probably be easier to edit existing mons, for them to have the right memories and other trash data (if applicable).

What I'll say is, use one of those free programs to check your SD card. You'll never really know if your SD is fake or bad until you check it. I'm not saying they intentionally sold you one, but sometimes stock get swapped and they wouldn't know either. Even so, the injecting of saves into the NAND resulting in NAND errors wouldn't be PKHeX's issue, but whatever save manager you're using. Any modified save wouldn't be causing NAND issues; at most the game wouldn't launch (saying save is corrupted) but the NAND would be fine.

It shouldn't. Perhaps you have a bad SD or a fake SD card (they programmed it to say it is a bigger size, but it is actually smaller than you think)

upload a screenshot of said example

While PKHeX has had legality issues since the new update, and I read that some people add a mon but it instead shows as lv 0. Despite that, I've never had any issues of that sort. I was able to wipe my PC and fully inject various mons (for screenshots), so I have not encountered your issues, and have not been able to recreate them. With that said, I am not denouncing any of the experiences either one of you had. Perhaps you guys adds mons differently from me. By chance, your method happens to encounter the issue, so when you continue your method, you continue to encounter the issue. As we're different people, I deviate from your method and unable to think up your method, thus never encounter it. Thus, the only solution really was you guys to provide a step-by-step, so that I can try to do it your way, in an attempt to recreate the issue.

I saw what you said, but once again: without a step by step guide, it's hard to replicate the issue. We gotta be doing exactly what you're doing. In the mean time, I can try the "not saving for a while" thing, but I honestly don't think that'll be any different. There's sometimes hotfixes to issues, where the hotfix is uploaded onto the site, and PKHeX won't prompt you to update. So you may think you're on the latest, but if you don't check the site, you really might not be. Thus I'm just saying

how odd. Have exact step-by-steps + images in a spoiler, and hopefully we can recreate it following the steps

@walppeople Use the latest version, provide exact steps that cause the mons to not show up in PKHeX. Granted, I've read that people have issue making mons appear in the game, I've never had any of those issues and couldn't replicate the issue. (unable to have correct presentation in game isn't same as not appearing in PKHeX) So it'll be great if you could give step by step instructions (and maybe screenshots) of your issues, so that we can try to recreate the issue. If we can't recreate it, we cannot fix it.

No worries, I'll like errors to get ironed out too

I just tried adding entries by creating them from scratch, and they were stored in the save too. You probably should delete your PKHeX then redownload. Can't think of any other solution cause only you're experiencing it and I can't replicate it.

Your "bulk" is editing them in one by one? Are you creating mons totally from scratch? or are you viewing an existing mons then making edits? I couldn't replicate the steps nor the error you're encountering.

I've imported by bulk before, and it works fine too. I used this, and hit 'Yes' Maybe it's the method of bulk importing. How do you bulk import?

what version of PKHeX are you using, and on Mac or Windows? My edits loads just fine. I'm on the latest version

Sorry, I gotta ask. Did you "set" the mon into the save? Did you save the save file?

I use my hacked Switch online just fine. However there's no way to prevent bans, only reduce the chance. I don't download custom themes, I don't pirate games for the Switch etc.

You mean legal. Legit requires the save to not even be extract. This should cover you.

The PID of that egg needs to match their OT TID SID

yeah, read wikis and documentation. They shuffle bytes around, add extra information, remove extra information. The most concise way is to explain the changes in structure, is to tell you to look up documentation. There's now 8 generations, excluding minor revisions that even occur mid-generation. (example: Poké Ball caught in for HGSS uses trash bytes that was unused in DP, so that the Ball data carries over properly etc) There is no way to adequately summarize everything that has been changed. edit: Bulbapedia has Gen 1 to 4 data structure. Our Technical Documentation, sorted by generations, has the data structure too. Whatever else isn't there, can be found on PKHeX, albeit in code.

Are you on updated PKHeX? I HA'd my Galarian Corsola (and Cursola), and it's not illegal.

@vicspanka Let me ask you then, where can you find HA Noctowl in SWSH, that can be used as a parent for breeding?

You could have modified your Switch's date to b4 the start date. Unlikely, but could have