Kaphotics

1. "Jump" is for jumping ahead/backwards a specific amount of bytes. Each instruction consumes a variable amount of bytes based on the amount of arguments it may have. The scripting execution environment just reads the script file, and based on where the current command is, it jumps somewhere else to continue executing next. https://en.wikipedia.org/wiki/JMP_(x86_instruction) 2. Scripts are self-contained, so there can be multiple scripts if the file header is updated to have the relevant count & offsets to tell the game where to find script # 7, for example. 3. Not all script commands are well understood/documented (at least at the time a post may have been written/updated). If no script commands had function names, only their command # (e.g. "6"), the only way to infer what they do is to observe how the game carries out the script code and how the if-else logic results in an observable effect in-game. Logic06 is basically "this command does something with boolean/comparison logic, and is script command 06, therefore we'll call it Logic06 instead of Command06".

https://github.com/kwsch/PKHeX/discussions/4355#discussioncomment-10534491

As mentioned, there is no legitimate transfer method/algorithm for Gen2->4. You can turn on the "allow incompatible transfer" setting, but it's not going to result in anything legal. Best you can really get is recreating via the encounter database.

Use PKHeX's encounter database to generate from template. If you want someone to trade it to you, just use a trade bot instead.

PKHeX finds a valid HGSS footer in the second save file (0x40000), which is somewhat true as evident by the box data containing PK4 data (not PK5 data). Use a hex editor and zero out the byte at 0x4F620. That will invalidate the build timestamp for the HGSS save, and PKHeX will then recognize the save data as White. You likely imported your HGSS data into the emulator and restarted it, which doesn't actually clear out that incorrect save data file. Thus, the old save data lingered in the unmanaged area and is causing your issue.

When was the event first available, and when was the program last updated?

Feel free to update Bulbapedia or submit a pull request to the above repository when you've fully researched any events you feel are missing and noteworthy enough to be included.

Depends what solution you are looking for. Was the Pokemon modified or not legitimately obtained? Signs point to yes. Do you want to keep it, and fix any issues, to make it legal? Then fix the OT friendship. Or, use the encounter database to generate a new one from scratch. Or, delete/release it. Do not confuse the OT's friendship value with the value of the current handler (save file)'s friendship value. Two separate values.

How can they have the Super Training Ribbon if it hasn't completed any of the Super Training regiments?

Just checked; the program doesn't support MetDate / EggDate randomization, only via a single value. If you wish to randomize, randomize each component of the date separately.

You don't need HaX to allow backwards conversion. It can be turned on via settings. But yes, you can't transfer something to a game that it doesn't exist in.

That's not the right syntax, you don't use [ or ].

Try to use the batch editor to set the properties for the trainer who deposited them: https://github.com/kwsch/PKHeX/blob/2cd9632c4aaaac36a451d6bbebef6312701aae30/PKHeX.Core/PKM/RK4.cs#L303-L323 OwnershipStatus might instead be the integer for which Mii owns the Pokémon. Replace the TID/SID/OT with values you'd expect to see for yours. .OwnershipType=1 .OwnershipStatus=2 .HandlingTrainerTID=1234 .HandlingTrainerSID=1234 .HandlingTrainerName=Me You can edit various features of the Ranch save data via the Block Data editor.

PKHeX does not support ROM hacks that modify the way the save file is stored.

File names matter, and not adding in extra files matters as well. Try restoring the save files to your Nintendo Switch to see if they work fine there.

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.