Kaphotics

1. This won't be legal if you're using a virtual console savefile (sav.dat) or Generation 7+ save file, as this is a Gen1/2-GameBoy Era only gift. 2. PKHeX doesn't recognize many gen1-3 events, because they aren't serialized into the program. Until the community serializes that data for PKHeX to add, it is up to the individual user to validate the unrecognized mystery gifts.

> They are LEGIT, do you know the difference between Legit, legal and illegal? , cordially. > I invite you to read this link, which explains what is LEGIT: do you even know who you are replying to? lol Your junk is ILLEGAL because it does not have a valid Raid RNG seed relationship, among other faults I won't bother mentioning. Due to the requirements needed to calculate such a relationship, it is not distributed within PKHeX. I suggest you educate yourself on the legality of Raid RNG prior to claiming your hacked junk is "Legit". Also, educate yourself on the difference of "Legal" vs "Legit", as indicated in your linked site: Anything modified is not "Legit", it is only legal at best. Tamper with a single value, and it is no longer unmodified. The diagram used by the site is wrong too. This is the correct version: http://pokemondatabase.weebly.com/uploads/3/5/4/5/354517/9236580.png?578x432 Legal and Illegal do not overlap. Using in-game glitches to obtain unobtainable data is not legal.

These are hacked, and not "legit".

Changed the "Some" to be 1-127 in latest commit

1. Use the advanced filters to !EVTotal=0 2. There's a new setting in the latest commits (since the last release) to bypass the "is present in current save" check. https://github.com/kwsch/PKHeX/commit/5636e1ef4aa433122894b074d00cdf17b46c466a#diff-08cc001c6c0d5099a6160e2fd220324221b119ec147e29281352a64152874c61

Marks are tacked on separately from the RNG that generates the overworld Pokémon.

1. Research requests aren't usually carried out by me, especially if they're for cosmetic / inconsequential stuff. It's up to the community to research how mechanics work, and I / others can implement them later. 2. Very few people elected to use the smaller sprites, and having to maintain two separate sprite banks is unnecessary bloat / handling.

Please try running the development build, hopefully there's a better error message: If not, might have to try debugging it yourself (installing Visual Studio Community 2019, and building the .sln yourself), unless someone else can replicate the error. I can also try recompiling a build that has some manual dumping for that call site...

Try putting this pdb file next to the exe and see if the error message is any different. PKHeX.pdb

Read the stickies.

It's right next to the executable.

Almost as if there's restrictions on certain encounters that always come with hidden abilities...

Not able to replicate with various language settings. Please attach your cfg.json file.

Memories window will show you both friendship values.

Then it has to be the base friendship for Gen7, for the OT. Creating things perfectly from scratch requires filling in a lot of things correctly.

Working as intended. Familiarize yourself with Technical Record legality and GO transfer friendship.

Done https://github.com/kwsch/PKHeX/commit/7e32ff9b03da15c9522e0e2061ace9e9c2ad4877

The sapphire save you've attached doesn't look like a valid save (doesn't have the block footers one would expect every 0x1000 bytes). Please double check that you: 1. have saved in-game (if using emulator). 2. have a valid cartridge (not a reproduction / fake).

Stop using save states. Export the save file from PKHeX and overwrite the save file. Restart the emulator and let the game reboot.

Regenerate the pkm from the encounter database.

Read the stickies. PKHeX requires .NET Framework 4.6 and above.

Already been reported and fixed, feel free to try the Development build, or wait for the next release.

VC Transfers show which version they were transferred from. For legality checking origins, it's whatever it matches to first. Generation 1/2 PKMs do not store the version they originated from in their data.

I checked the save data in a hex editor, it doesn't have any of the "POKE" magic markings that a normal Stadium 2 save file would have. I tried force loading it as a Stadium 2 save file, and the data was junk. Are you sure that this was exported from a Stadium 2 game? Does it work on another emulator when imported?

Assuming you are using a save file that has been correctly saved within the game, PKHeX should be able to open it regardless of byte-swapping. We cannot provide assistance beyond telling you to double check that your exported save data is correct (open in a hex editor to ensure data is actually present), as you have not posted the save file for others to inspect.