Kaphotics

I'd say to just use the Misc Editor to re-create Pokéblocks and repeat the process. Recreating the pokeblocks is less hacked than recreating the mon

Bad dump; it appears that the dump has many "stuck/flipped bits" where the top bit of some bytes is stuck "on". To get the save file to load in PKHeX, I had to force specific bits to be off: The save block ID used to have `08 80` for block `08 00`; I manually changed the first set of save blocks to have a revision counter of a lower value so that the other half of the save file would try loading, but after noticing the party missing, it confirmed that more flipped bits were present. Some save blocks revision counters were 94 02; when comparing it to 9C, it also has the top bit of the nybble flipped. Party data starts at offset 0x238 of block 1; the party data is seemingly present, but the random bitflips make recovering anything an extreme annoyance for very little gain. Here's the party data if anyone wants to look at it (100 bytes per party pk3). 9B 2A EF 3F 14 64 70 66 C0 BF BF BC BB CD FF 08 0A 00 02 02 C7 E3 DA DD EC EC FF 08 AC CE 08 00 19 4E BE 59 8F 4E 9F 59 A7 6D 9F 59 8F 6C 0B 78 07 BB B8 58 8F 4E 9F 59 8F 4E 9F 59 8F 4E FB 0B EB 0A ED 09 C7 4F 9F 59 8F 7C 9F 59 8F 08 9F 59 00 00 00 00 14 FF 2F 00 27 00 0D 08 10 00 28 08 0D 08 1B 08 2F 7A AA FC 75 8F 1B 3B CD CF BF BB CC C9 C6 BF FF 8F 0A 02 C8 BB C9 CC C9 CF B5 00 B2 87 00 00 F2 F5 22 CF BC FD FE CE 4A FA AD CA B9 F5 73 CF 79 E7 B3 CF 59 4F B1 CF 1A 3F 19 EE 8E EA C8 EB 5A 7D B9 CF 5E 0B B9 33 5A FD B1 CF 5A FD B1 CF 08 00 00 00 37 FF 89 08 89 08 55 00 2F 08 84 00 1B 08 40 00 AC AD 7A 26 AB ED 1F BC BB DC BB CF CB DB BB CC FF 00 02 02 C8 BB C9 CC C9 CF B5 00 26 D4 00 00 47 15 AB 8A 0A 8D DE B8 0F C0 65 92 56 41 54 92 14 40 2B 9A 1F 4F 6A 9D 99 41 6D 9A D7 52 7E 9A 04 DD 6D 9A 52 E3 09 A9 1E 0E 6D 9A 07 40 6D 9A 00 00 00 00 64 FF 62 01 62 01 61 01 E3 00 C2 00 42 01 F7 00 33 0E BB A8 7D 8F 1B 3B BC CE C3 CD CD BF DB FF 00 00 02 02 C8 BB C9 CC C9 CF B5 01 35 3B 00 00 B4 81 A0 93 2B 0E A1 93 46 7E A0 93 58 CB 94 B6 59 98 A8 93 46 81 A0 93 06 A1 20 B2 BF 23 0B 3E 4E 01 A0 93 69 89 27 93 91 81 FF 9A 49 8B AD 87 00 00 00 00 32 FF 4B 09 4B 09 1E 00 1B 08 4C 08 60 00 9A 08 09 18 4F AB 9F 3E 99 94 CA BF CE C3 CA CA BF CC FF 43 02 02 C7 E3 DA DD EC EC FF 00 8B 8E 08 00 A8 2F DE 3F CB 6F DE 3F 9E D9 DE 3F 8D 2E E7 3F A8 2E 68 3F 99 29 C8 35 DE 29 CF 9E 8C 5A F4 3E 9E 2E DE 3F 9F 2E DA 3D 9F 2D DE 3F 9E 2E DE 3F 00 00 00 00 1A FF 4F 00 47 00 1F 00 46 00 2C 00 2F 00 29 08 E6 B8 4C B6 AC 79 09 E9 BE CF C8 CD CA BB CC BD BF FF 02 02 C7 E3 DA DD EC EC FF 00 A4 D8 00 00 0A 5B 59 FD 5B 88 4F 5D 4A C9 4D 5F 4B C9 4D 5F 4A C9 4D 5F 4A C9 4D 5F 8C C9 4D 5F 4D E9 4D 5F 4A 3E 4D 5F 29 C9 2A 5F 5B C8 0B 5F 5E E1 47 50 00 00 00 00 14 FF 4B 08 4B 08 22 00 24 00 1B 00 22 00 1B 00 I'm not wanting to try random permutations of bit flipping to try and recover data. I've seen this issue happen once before, and was able to do 1 pokemon manually for them (it was a precious shiny). I can let someone else try for your case ^ example of bitflips; the block shuffling is garbage because the shuffle order value is bitflipped, among other values in the pk3 structure. PELIPPER => PETIPPER CE <= C6 1100_1110 = CE (char T) 1100_0110 = C6 (char L) obvious bitflip on the lower nybble.

The program does not render the dex skin to a visual image. Try loading the save file to your cartridge after exporting.

Latest commits of PKHeX no longer flag these PP values if they exclusively match the VC's values Add Gen1/2=>7 VC pp table & check bypass · kwsch/PKHeX@c6cde06

Personality value - Bulbapedia, the community-driven Pokémon encyclopedia

As is the case for rebuilt roms, you have to remove any installed patches otherwise the patch will override any changes to the base ROM.

You need to install Wine as well, not something out of date. The error log you attached can be used with a Google search to see what versions of Wine are updated enough to expose the Operating System calls that the program needs to infer display resolution. https://forum.winehq.org/viewtopic.php?p=142603&sid=e72c577c65a41ca794479ade5ee55b2c#p142603

I think not. Manually making things requires a laundry list of considerations to be done right, and you likely don't fully understand what all the values need to be. Use the encounter database, and compare the verbose report to what you're manually making.

PKHeX is open source; reference the source code. Nobody is going to write you a plaintext novel on how each is generated when the source code already provides the start->finish logic. PKHeX/PKHeX.Core/Legality/Encounters/Templates at master · kwsch/PKHeX

Connect online to Nintendo's servers and download the latest game patch. Dump the patch contents, same as you did for the base ROM. Then merge the two folders so that there is only one romfs and exefs.

Read the message. pkNX does not work on unpatched game files.

PKHeX/PKHeX.Core/Resources/text/script/gen3/flags_frlg_en.txt at master · kwsch/PKHeX pokefirered/include/constants/opponents.h at 70b76a15df8c6a6dd03d7a09e8f9eddd2e4dc29d · pret/pokefirered (opponent flags start at 0x500, so 1718 - 0x500 = 438) pokefirered/data/scripts/hall_of_fame.inc at 70b76a15df8c6a6dd03d7a09e8f9eddd2e4dc29d · pret/pokefirered It's automatically cleared when you enter the hall of fame, so you can consider it a "temporary" flag.

Refer to the source code license regarding permitted uses. If it's hosted on GitHub, chances are it's already been ingested by someone at least once already, so using it for your own understanding/translation is zero harm, zero issue.

Relearn Moves for eggs are the moves it knew at birth (when it was created as an egg). If the two parents only passed down one move (Petal Dance), then that's how it is. How statistically likely it was that the two parents were set up to pass only Petal Dance is irrelevant to the legality, moreso the plausibility. Suspiciousness is up to you.