Kaphotics

Lucky you, I reverse engineered a 14 year old program to convert its functions into PKHeX for Gen4 battle video ripping See attached Uxie (assumed Platinum Acuity Cavern, since Version & Location aren't saved in battle videos), along with all 12 unfixed participating Pokémon. Other small things like Met Date, Ribbons, and Contest Stats are also not stored in battle videos, so you'll have to restore those however you see fit. 0480 - UXIE - B8F264593D2E.pk4dump.rar // ripped from offset 0x27000 (extdata block 02) var data = File.ReadAllBytes(@"D:\Kurt\Desktop\test.bv4"); var bv4 = new BattleVideo4(); bv4.Decrypt(); foreach (var pk in bv4.GetTeam(0)) File.WriteAllBytes(@$"E:\dump\0_{pk.FileName}", pk.DecryptedPartyData); foreach (var pk in bv4.GetTeam(1)) File.WriteAllBytes(@$"E:\dump\1_{pk.FileName}", pk.DecryptedPartyData); https://github.com/kwsch/PKHeX/commit/802974a42c91d209cc75c383b09402136ca8beea

This thread is for reporting issues with PKHeX for legitimate pokemon, not for issues with other tools. https://projectpokemon.org/home/forums/topic/64728-pid-mismatch-shadow-gligar-colosseum/

From PKHeX: // Version is not updated when hatching an Egg in Gen3. Version is a clear indicator of the game it originated on.

The checkbox for Owned indicates if you own it and have registered it in your dex. If you hacked it in without registering it to your dex, that would explain the missing check.

Well, if you dumped your ROM to play it on a flashcart, then you have access to homebrew and the original cartridge. Flashcart-specific dumps that are not decrypted are not usable in any program like PKHeX. You need to decrypt the file, which is unrelated to PKHeX (and this site).

It means exactly that. It's not a save file format that PKHeX can recognize, therefore it rejects it. Export your save file from your console/cartridge correctly, with homebrew.

That's not a valid save file. Export it correctly from your console using homebrew.

fixed on latest ty

You're not using the latest version of Wine.

PKHeX does not support ROM Hacks. Ensure your emulator is exporting a proper save file. The program does not know what modifications an emulator / rom hack make to a binary save file.

Empty/blank lines should not be included in the text box. Ensure you have only entered two lines, and that all lines you have entered are "complete" instructions.

Check the randomization settings. Low-powered moves are intended to be given instead of higher-powered moves, for a more balanced early level experience.

If the checksums are invalid, then all you have to do is export the file from PKHeX and it will apply the correct values. It is important to ponder why the checksums were originally invalid -- did you manually modify the save file? Is the dump actually "complete" and not a glitched dump from dirty cartridge contacts resulting in bad reads? Is it from a ROM Hack which has modified the save structure, resulting in different checksum locations or calculation methods?

Each SaveFile object exposes an `Inventory`.

You didn't export your save correctly. Save states are not save files.

Master Ball cannot be inherited via breeding.

Then you didn't export your save data correctly. The 3DS stores its files encrypted on the SD card to prevent people from tampering, which is why you need to use homebrew to export correctly.

Resolved on Discord; the OT Name that was set to the PKM via batch editor had a leading space; end result was that the OriginalTrainerName did not match that of the save file, so HT data was being reapplied (intended). Ensure the OT name matches that of the save file

Your save file is not valid. Try exporting it with homebrew again.

Inside the program's settings for the encounter database you can use the main editor to provide criteria for the template generator. If you have a desired nature, gender, ability, etc, it'll try to match whatever is allowed.

PID/IV correlation exists.

Emulators should be able to export raw save files without extra emulator-specific metadata. PKHeX should not be responsible for supporting whatever arbitrary format the emulator/ripper decided to package the savedata as.

Your hack has modified the savedata structure; PKHeX scans to make sure things are "proper", and your save is not. The first savedata object is expected to have a size of 0xF628, but it seems yours is 0xFBE0 (larger). The box storage object is also too large, coming in at 0x1E4FC (not 0x12310). So, your save struct is different from what PKHeX expects for a valid HG/SS save file, and is thus not an HG/SS save file.

The game disallows an all 0 trainer id

The answers for vague questions like this is always "it depends". Changing values after something is generated is only "safe" if the encounter is not locked into a specific requirement/correlation of values. Not every correlation is checked by PKHeX, so it's up to you to research and understand.