Author's Note
Hello all, always save twice in-game before using this program,
and always keep a safe backup of your saves, as a safeguard against unforeseen corruption.

Note that Gen 3 info stored on the save is rather bare, compared to Gen 4 and Gen 5 entries.
In any case, you gotta use PKHeX to fix all the legality problems (ball, location, IVs, moves, abilities etc). Use at your own risk.

Information regarding PID->IVs calculation
Purpose for adding this, is to aim to make it easier to revive possibly legal mons from the Hall of Fame.
All entries generated are using some form of Method 1 method. Event/XD/Colo Pokémon will need to fixed manually by users (since most identifiers for those aren't retained in HOF, so only user would know)
1. Legends/Unown will directly use Method 1/Reverse Method 1 IV calculation based on PID.
2. Other mons (which were set to be hatched by the program) will still use Method 1 for calculation, but for legality sake on PKHeX, it's HP IV has been reduced by 1. (Hatched mons cannot have Method 1 IVs; will be read as illegal on PKHeX)
3. For Gen 5 and onwards, in most scenarios PID and IVs are no longer linked.

Known issues in general
Any of these entries should be fixed by the user:
1. Using the default loaded mon on a Hidden Grotto capture will likely cause it to be illegal.
2. Event mons will likely be illegal
3. Pokémon of XD or Colosseum origin will likely be illegal
3. Cute Charm mons in Gen 4 will likely be illegal. (I'm imagining if they were imported up, this issue will also exist on later gens)
4. In Gen 5, shiny Tornadus, Thundurus, Landorus, Ho-Oh, Lugia, Dialga, Palkia, Giratina will be illegal (cause their default load entry is the Dream Radar version)
5. Legends/Unown separate default loading has not been implemented for Gen 6.
6. In-game trades from Gen 4-6 have not yet been implemented.
7. In-game trades from Gen 3 have not been implemented in Gen 4-6.
8. Beyond Gen 3, extracting Pokémon that couldn't learn Hidden Power would end up illegal. ()
9. Most Pokémon extracted in Gen 6 would probably be illegal, due to lack of Egg Moves.
10. If your Pokémon had an illegal PID/Moves/Nickname-OTname combination etc, PKHeX would naturally flag it (duh)

Fixed: Gen 4 had issues with injecting Pokémon files. (Bug introduced somewhere after 1.2.7). Written a quick fix. If any issues, message me. (The program crashed when injecting mons, related to converting pk4's experience to a HOF lvl)
Hot Fixed: All boxes are grayed out/disabled. Having them enabled may mislead people into thinking those entries can be modified.

--------------------------------------

Previously, on Version 1.3.2

Added: Gen 4 and Gen 5 - Language identification (JPN, KOR or ENG, based on nickname and OT name)
Added: Gen 4 and Gen 5 - Automated Calculation for PID to IVs
Fixed: Gen 4 and Gen 5 - Matching of abilities had a slight glitch, had been resolved
Changed: Gen 4 and Gen 5 - Legends and Unown now use their own default pkm loading, for more accurate location and encounter detailsnote: location details would only be accurate for in-game encounters, not for mons received from events
Fixed: All Gens - Empty entries that were selected no longer get dumped
Changed: All Gens - Overall cleaning up of code
Changed: All Gens - Clearer message, whether the save used was incompatible, or no Hall of Fame entries located in save.

Changed: Gen 3 - Legends and Unown now use their own default PK3, for more accurate location and encounter detailsnote: location details would only be accurate for in-game encounters, not for mons received from events
Changed: Gen 3 - In-game trades now use their own default PK3, for overall more accurate details
Added: Gen 3 - Support for International Encoding system.
Fixed: Gen 3 - Nicknames of in-game traded mons that use special characters (normally not selectable by player), have the special character displayed as Japanese.
Added: Gen 3 - Language check now exists (JPN and ENG only), based on characters in nickname.
Fixed: Gen 3 - Japanese nicknames does not display correctly on PKHeX, when language byte isn't JPN. (read above point)
Fixed: Gen 3 - Issues with Japanese nicknames displayed and transferred to pk3, especially those from in-game trades.note: they have weird leading bytes in their hall of fame entries, that throws off both the display system and the pk3 files

--------------------------------------

Previously, on Version 1.2.9

Added: Gen 3 - if the HOF entry has the same TID/SID as the save, save file's OT name and OT gen will be utilized for the pk3 extracted.
Added: Gen 3 - save's game identification (based on the game code in the save)
Changed: Reworked how experience was derived from levels.
Fixed: Gen 3 - After viewing 30+ overall HOF entries, going back to earlier entries caused them to not show up correctly
Fixed: Gen 3 - Nickname in textbox may overflow and read an extra byte, thus leading other nicknames to look corrupted when cycling through entries.
(this does not affect actual nicknames sent to pk3, though)

--------------------------------------

Previously, on Version 1.2.8

Fixed: Dumping any entry in a page that contained a creature from the fast experience group could result in an exception.