Kaphotics

Thanks, fixed: https://github.com/kwsch/PKHeX/commit/1c0b2488ef323b4cca00fd7562dfe7c8d971f1e7

You're probably doing something wrong when you're restoring the save data. If something was (simply) wrong with PKHeX, there'd be a flood of reports.

Edit them in HxD or any other hex editor. Reference structure is at the bottom of here: https://github.com/kwsch/PKHeX/blob/029e0e0a0801d2d6075bcca32cb6a0736deb1543/PKHeX.Core/Saves/Substructures/Gen7/GP1.cs

That's probably not saved in the PKM data, it's likely in the save file which gender it is. I don't think anyone has found where that info is stored. The game shouldn't have to dig through the pkm storage to find your starter, then to check the gender. It's likely precomputed and stored for easy reference

Read the source code, or find a website that lists the new game's data.

Read the changelog.

Please elaborate.

You can import & export gp1 files, and dump the current contents. Whatever is in the editor is what's currently available.

example: folder name, tab, path.

The batch editor is the go-to for finding what properties are named; they're the same as those used in the Advanced Search. =PKRS_Strain=0 ^ never infected

I looked into the savedata stored for GO transfers, and the Move IDs are retained. If you've transferred things already, just leave them there. We may have this as an 'event gift' format file that can be shared and injected into save files.

The error message contains details on what went wrong. System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\Nick\AppData\Local\Temp\380 - Latias - 43D47CF38197.pk7'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) Likely your antivirus is preventing PKHeX from creating temporary files, which are used for facilitating drag/drop.

"Complete" needs to be checked, since you've completed training. It's what the legality message is hinting at.

Manual selection is already implemented; hold control when importing to bring up the selection. Version detection isn't perfect for Gen3; PKHeX uses Bulbapedia's detection method which isn't correct. https://bulbapedia.bulbagarden.net/wiki/Save_data_structure_in_Generation_III#Game_Code https://github.com/kwsch/PKHeX/blob/668b8611d51e0e0b28240508026b4c0ae1f1ce33/PKHeX.Core/Saves/Util/SaveUtil.cs#L230-L249 The ROM disassembly indicates that this offset isn't game code: https://github.com/pret/pokeruby/blob/51ecf10029f84dd5423cd59582d01eaee9140c0e/include/global.h#L822-L844 In the future it'd be nice to have a more foolproof detection, but for now, just override if it's incorrectly detected. (edit: future versions of pkhex will have improved detection logic for RS<->E differentiation)

There's no way to modify the Catch Rate byte unless you trade it to Gen2. If the Catch Rate value does not match any of the possible encounter species, it's not valid (it can't ever be changed). Since the value is different, it was modified, hence flagged.