Kaphotics

You can't set console dates that early, hence the error. Use the Block Editor.

In cases where multiple different encounters could have originated your Gloom, the program simply picks the first one it finds that is valid. Oddish can be captured in the Safari Zone area 3 at levels 27 and 29. Gloom can be caught at level 29 and 31. In your left instance, you have a level 29 Gloom. Assuming the met level is 29, it couldn't have been an Oddish, because it must level up at least once to evolve (but it was met at the level it currently is). In your right instance, you have increased the level. Since the current level is above the met level, it no longer disqualifies Oddish from being one of the possible origin encounters, and when it finds Oddish first, it further validates it as possible and yields. Both say it is legal, so there really is nothing to worry about.

Use the encounter database. The program is correctly not matching your hacked data. This thread is not for users having issue generating data correctly, only for legitimate obtained data being flagged.

PKHeX supports all mainline games and side-games that can link with official Pokémon data, including BD/SP. It does not support ROM hacks which alter the game structure, and requires you to export your save data properly without console encryption to read the file.

Patch is to modify an official patch file, which already has rom2 (SD card) references. There's no real need to use it anymore since layeredfs exists.

For it to be having a current handler of the OT, it must reside on the OT's save file. If your save file loaded does not match the OT details, then it is currently being handled by the not-OT.

Use the Pokedex editor. It has buttons for what you are asking for.

Try to comprehend what the message is saying; the trainer that currently possesses the Pokemon does not match the expected state. If the save file is not the OT, then the current handler must not be the Original Trainer (OT).

Use the encounter database after loading your save file into the program.

No, they're hacked shinies without a valid wild PIDIV, so they could only originate from eggs, which can only be in Poke Balls. Not an issue with PKHeX. This is only for reporting legitimate pokemon that have not been modified in any way.

Uninitialized (all zero) means exactly what it says -- the file size might be right, but there's literally no data in the file. It's not a valid save file / dump. Not an issue with PKHeX. Save File sizes are not 0x2000, they're at least 4x bigger than the file you're trying to load.

My recollection is that there were never any Battle Tests distributed during the lifetime of the NDS online services, so this content was never officially available for download & documentation. As the years have passed, our understanding of the Gen5 save file structures has allowed us to identify the region of save file data that *would* have stored the downloaded battle test data, were it ever made available officially. However, since we don't have any of the official data, we can't really guess the size & layout of the data that needs to be there to get the game to recognize it. With the power of disassembling the game code, we can see that the region of data is 0x5C8 bytes long, and the validation function checks for a magic number and checksum over the region being valid. When it's valid, you get.... == The latest commits of PKHeX allow for importing/exporting of this data region. This "DLC Battle Test" structure is undocumented. Fuzzing the rest of the data to values 01-04 gets me into a battle! Guess it has to be analyzed in more detail, but hey, at least we can trigger the in-game loading of injected data! Attached a randomly-fuzzed download test that doesn't crash, which can be imported with the latest development build of PKHeX. Rather than disassembling the game code that interprets the block, we can just observe the results and see what offsets determine what, to get the overall structure documented Battle Test.bt5

Use the batch editor to set SpeciesInternal to whatever game-specific Species ID you want.

"Why is a hacked pokemon being flagged as impossible to obtain legitimately?" Read each line. Use the encounter database instead of guessing values.

Main is completely 00 00 00 00... so there's no data. Backup is 40% random data, and the rest 00 00 00 00... so there's nothing recoverable.

Already reported & fixed on latest development build: https://github.com/kwsch/PKHeX/commit/9d06a2bc2d0ec5f7c0f020acd73a2144a4d30c2c

Change the filter to search for something. It's not going to give you a list of every single encounter for you to manually scroll through unless you change the settings. Gathering the full list isn't instant; it's a short-circuit to prevent you from wasting time. Use the filters.

Sure you can spawn it, but it won't be legal or transferrable to HOME.

You have to search for something first.

Nope. What you saw online is a method to obtain a "key" to decrypt the save file, but doing so requires the cartridge. Which you do not have. Powersaves backups are useless without the original cartridge.

Nope. You need the original cartridge, as Powersaves backups do not contain the cartridge-specific data needed.

Every starter (and captured Pokemon) is generated with a traceable pattern by the games, yet yours does not follow that pattern. Either you changed the PID or you changed the IVs with cheats, glitches, or tool/editor like PKHeX; knowingly or unknowingly. There is not a way to obtain what you did without cheating. What exactly you did? I wasn't there when you obtained it or every period of time you interacted with your game data; only you can know for sure. Calculators exist. https://sites.google.com/site/ivtopidapplet/home

PKHeX will never be able to generate data directly into HOME. The program is a SAVE FILE EDITOR. You can never hack a "legitimate" Pokemon into existence, only "legal" Pokemon. A legitimate Pokemon is one that was obtained with normal gameplay. It either is obtained legitimately, or it is hacked into the game. Whether it is legal or illegal depends on if it is indistinguishable in comparison to a legit Pokemon.

The currently loaded save file is the player that is possessing the PKM data. If you have not loaded a save file, then the default save file (PKHeX) is the one that possesses the data. The pointer as well as the trainer data must be correct.

Not legit; needs to have a PID/IV correlation that the program is correctly flagging. It needs to be a "Method 1" PID. Assuming the IVs are unmodified, the PID should be F964768A.