Kaphotics

GameFreak/ILCA do not have advanced legality checks in their official validator, especially none that have ever checked for RNG patterns their games have had. It is up to you whether you continue to risk, as PKHeX's checks are indicating that it was tampered with.

The Trainer ID is that of the save file; it must be possible to hit the Trainer ID/SID from any starting frame of the Naming Screen. Pokefinder's TID/SID search does not account for the naming screen's RNG pattern prior to when the TID/SID of the save file is assigned. PokemonCoRNGLibrary/PokemonCoRNGLibrary/Util/LCGExtensions.cs at e5255b13134ab3a2119788c40b5e71ee48d849b0 · yatsuna827/PokemonCoRNGLibrary

1. The TID/SID of a Pokémon is that of its original trainer, who first obtained it. 2. You shouldn't have more than one unique encounter from a trainer. 3. It means exactly what it is labeled as; it is the trainer who has most recently handled the Pokémon. If it does not reside on the Original Trainer's save file, then it resides on the Latest Handler's save file (ignoring HOME basically not being a handler). 4. No. See #1. 5. Depends. Everything "depends". If it was able to visit Gen3/4 to participate in the Battle Tower/etc, then it should have sufficient level to have participated. 6. "Dangerous" no, "suspicious" yes. Do the mental math on how statistically possible it would be for you to have obtained it without cheating. 7. Having default/non-special memories is suspicious, because it's a sign they weren't really used in-game. If they have special ribbons and stuff that would have naturally obtained those ribbons, then you'd think you'd be more likely to have uncommon memories. Likewise the opposite; if everything has uncommon memories, that is suspicious too. 8. All auto legality mod does is generate things from the encounter database and update them to the battle template set you asked for. If you know how ALM's code works, you can see the patterns in how those are generated, and they're pretty obvious. tl;dr - use bottle caps and learn how things actually work, else you'll produce obviously-generated 'mons.

Sure, you can continue trying and compare your dumped data in a hex editor (like HxD) to see if you're able to obtain something different.

Bad news, nothing is present in your attached file that can be salvaged. Save data structure (Generation III) - Bulbapedia, the community-driven Pokémon encyclopedia Your save file only has blocks 3, C, & D present; everything else is FF FF FF... meaning uninitialized. In blocks C & D, they are all zero except for the box names being present (BOX 1, BOX 2). Block 3 is basically all zero besides a couple of bytes that aren't Pokémon. Nothing to recover, since everything is matching a "new game" state. Your save data, when viewed in a hex editor, as reference:

Thanks, fixed on latest commit. PBR: retain party stats, recognize party size · kwsch/PKHeX@c46596c The latest development build should allow for importing the files that are 220 bytes.

Thanks, fixed on latest commit: hatch4: permit rotom's room in hg/ss · kwsch/PKHeX@8ea0ee0

View an empty donut then clone it to all other slots.

Are you using any sort of screen reader / screen translator app? This error only recently started being reported. PKHeX crashes when displaying Legal Legality Report – TaskDialog GetBoundButtonByID · Issue #4852 · kwsch/PKHeX Also, try restarting your computer. This doesn't seem like an issue with PKHeX, moreso something interfering with what the operating system yields to the GUI.

That PID is not shiny for your TID/SID. There is no way around that. Use the encounter database with your save file loaded, use the criteria tab to specify the Nature/Gender/Shiny state, ideally without restricting the IVs to anything specific besides 2 (like Attack & Speed 31). Find the encounter with the search settings, then view it.

Picture speaks for itself:

Put whatever numbers you want for whatever stats you want.

Use the Misc editor, there is a Records tab.

There is no progress in this save file (it's before you named your character, aka no progress).

Save states are not save files (save data). Save properly in-game so that the save file is correctly flushed to the storage device. Save states are RAM snapshots of the emulator's RAM as it runs the game, containing everything about the current game play state. Save files are the savedata binary that the game encodes to save its progress when the game/console is powered off, allowing it to resume from the Game Continue screen.