Atrius97

See the relevant PID Mismatch guide for what encounter/origin your Spiritomb is from:

Just some feedback, it might be a good idea to make it clear that bypassing HOME via any methods will result in illegal Pokémon. This will work for singleplayer on Switch games but attempting to use HOME will likely trigger Error 10015 as they lack valid HOME data, and they could be caught by other online anti-cheat measures in the future. (You did make that clear in the Github readme, but not in your post here.)

It was an unreleased event item. It's not listed with the other wondercards and event records because there is no officially released wondercard for it. There's nothing for us to upload. If you want it, give yourself the item and set any relevant event flags manually via a save editor like PKHeX.

It's the case for SV raid encounters, as those have a limited possible number of RNG states, and can be detected easily if all stats do not align with one of the possible RNG seeds. As for SV wild pokemon, they are legal with 6IVs, but the odds of running into a wild SV pokemon with 6 Best IVs is 1/32^6, or 1/1073741824. As such, they're easily detectable as hacked by just looking at the Stats Judge function, since the odds of one occurring naturally is so astronomically low that you can almost certain it was hacked. To give some perspective on how low those odds are, if all 8.2 billion people on Earth ran into a wild SV pokemon at the exact same time, the chances are so low that it's likely only 764 people would find one with 6 perfect IVs. It might be legal because it's technically possible, but it's pretty reasonable to assume that you're not that lucky, and did in-fact just cheat.

Please try the latest dev build and see if the issues still occur:

Could you upload examples of the savefiles, specifically the unmodified savefile, and again after opening it and saving in PKHeX? Recording a short video clip showing the process from start to finish could also help identify any mistakes you're making along the way that's causing the corruption, if any. It's hard to know what's happening without being able to see the steps you're taking, or having the files for comparison.

There does appear to be *Bool KUnlockedHairSalonUpgrade02 in the block data. I'm unsure if that's what you're looking for, but I don't see any other "hairstyle unlock" blocks in the documented block data so far, which could mean the changes you're after are indeed not documented yet.

It also claims open source programs like PKHeX is a virus. By all means, you're welcome to not use it, but when you're dealing with cheat tools and homebrew software, you get a lot of false positives by anti-virus.

Well, the pins don't look damaged at least from what I can tell from the second photo, so we can assume the save data itself is corrupt. You have two routes to try if that's the case: A: On the title screen, press Up on the D-pad, Select, and B buttons simultaneously. This should bring up a prompt to delete all save data. B: If you have a hacked 3DS, you can use savefile manager homebrew software such as JKSM, Checkpoint, etc. to wipe it manually. If either of those options work, then you should be able to start a new savefile and play it. If not, the pins may be damaged even if they appear fine and you've cleaned them. It may also be an issue with the DS, so you can try using compressed air to blow out any dust in the cart slot, (and please use a can of compressed air or air compressor, NOT your own breath. Water-vapor on your breath can cause water damage, blowing into your cart slot/into the cart can damage it more). You could also try applying a thin layer of tape or something else to the front of the cart so that the pins on the cart are wedged more firmly against the contacts in your DS. If none of the above solves the issue, the cart is likely damaged internally, and there's not much information available on how to diagnose and repair the issue.

Modded consoles can go online in sysNAND/sysMMC. Going online in emuNAND if you've already been online before in sysNAND (or vice versa) is bannable. See https://nx.eiphax.tech/ban for more information about ban risks.

If every possible set of values is possible, there's no correlation for PKHeX to check. With eggs, the number of possible sets of PID, IVs, Nature, Gender, etc. is far larger than other encounters, to a point that every combination is possible and can't be traced back to any specific seed. Even if you "manually input perfect IVs or even change the nature", it's still displays as legal, because it IS legal. As Kurt said, having an "origin seed"/PID Type doesn't apply here.

By correctly dumping the game ROM from your legitimate physical copy. That aside, Kurt wasn't talking about the ROM, he was talking about the emulator itself. Some are more accurate than others, and depending on the emulator and settings, it can give you RNG results that would never occur on an actual physical console.

This isn't an issue with PKHeX. It's not designed to work with ROM hacks in the first place, and judging by reports from others, it seems that Kaizo is not fully compatible with PKHeX. Either: 1: The changes aren't being saved because the savefile structure is different, 2: Emerald Kaizo may have built-in protections against cheating and is reverting to the last unmodified backup (since it is intended to be a hardmode version of Emerald), or 3: You're not saving/loading the edited savefile properly. Arguing with Kurt, (who literally developed PKHeX and is trying to troubleshoot the issue), is not going to help you, so I'll be locking this topic. That aside, it appears there are other projects with editing Emerald Kaizo specifically in mind (you can either build it yourself from github, or there appears to be a download link in the Youtube video description): https://github.com/May8th1995/forkaphotics/tree/master https://www.youtube.com/watch?v=GjjSwzL2avA

That project is extremely outdated. "The advice has always been "use the latest wine and whatever PKHeX normally requires"." https://discord.gg/tDMvSRv https://discord.com/channels/401014193211441153/679178558597496872/1228758200279629884

This is a feature, not a bug. Also, Gen 1/2 have no personality value, so please don't report issues that don't actually exist for a given generation. This only happens for Pokémon generated in Gen 3 and 4.