Kaphotics

Re-read the first post of this thread. This is not for assisting with generated things. LGP/E only have 5 evaluated sizes: XS, S, AVG, L, XL. Future games added more evaluations.

You'd have to correlate them to how they're used. Oybn is alpha Pokemon Swm is likely swimming water encounters Gmk is gimmick (tree shaking) Mas is mass outbreak They're just internal names for the developer to differentiate things.

Should be in the text dump, but a brief inspection shows many duplicate names (assumed styles / gender-specific variants). dressup_item_name 1,000 lines, have fun dressup_item_name.txt

Again, via a trade bot? Trade bots by default zero out the HOME tracker to prevent duplicate trackers entering HOME. https://github.com/kwsch/SysBot.NET/blob/dbfd397ae9790078fa8bfaec308687bf3774872b/SysBot.Pokemon/Settings/LegalitySettings.cs#L75-L76

Again, boxed Pokémon do not store the current stat values. PKHeX works by loading the Pokémon's data from box, then checks if there's any existing stat values to display. If there are none, it regenerates them based off the game's stat calculations. Then, it shows the stats. If stats were available (eg, read from a Party slot) it would show those instead. Since no stats are stored in the box, the program regenerates them instead of showing nothing/zeroes, hence things differ from what you see in-game. All PKHaX does is just allow you to tick "manual stats", which disables the program from recalculating them when stats already exist (party) or when you change other stat-influencing things like Species/Form/Level/etc.

Boxed Pokemon in generation 5 do not store stats, so the game recalculates them on the fly. Since the stats are not stored in the box, PKHeX has to guess what the stats are, instead of showing zeroes. PKHeX does not support ROM Hacks. Whatever functionality you see is what you get; don't expect perfect behavior.

Check the trainer details tab. If it originated from a different save file, then it cannot be currently handled by the OT. Same for the opposite case; if it originated from the save file, then the OT must be the current handler.

Yes, dump your ROM from your console and use pkNX to view/ dump it.

The database shows Pokemon from all sources; backup save files, box slots, party slots, etc. The order should be irrelevant. You're supposed to use the search functionality on the right

That's not a save file for LGP/E; file is the wrong size and is all zeroes (00 00 00 00...).

SID, Version, and OT Gender matters for the CHANNEL Jirachi's PIDIV correlation.

Save files do not have this. Export the save file not as an sps, but as a sav.

Yes, the next release will have this fixed; eta not yet. You can compile it yourself if you must, or grab it from the Development Build page.

Fixed on latest commit: https://github.com/kwsch/PKHeX/commit/e53ca4b1af0288765998c4dd90acf478b6c835dd

This is not a PKHeX error. Plugins issues should be directed to the plugin author, not the main program.

no

Underneath that popup is the list of flags that were changed; there's more than 1 that was changed.

Clean your cartridge and ensure the save data is correctly written back to the cart.

VC save files are ALWAYS called "sav.dat". Besides filename, the file data is the same as it would be for a cartridge dump. The filename differentiation is used in order to permit certain mechanics/encounters from the GB Era like Pokémon Stadium, or disallow them (unavailable in VC).

Party stats are stored at the end. No party stats for boxed data -> all zero.

Gen1/2 encounters (besides Crystal) don't store Met data, so PKHeX has to try and guess what encounter it was. There's a lot of matches, so it just picks the first one since any could be true.

Resolved on latest: https://github.com/kwsch/PKHeX/commit/081a48bbf6ffb59d00cd62db178e85efb044c384

Unable to replicate.

The official legality checks do not care about RNG restrictions, but fan tools can catch things you modify. As is always the case, the answer always depends; does the encounter have an RNG correlation that generates immutable values, and is this correlation reversible back to the original seed? If the answer is yes, then the correlation can be checked & validated to see if the immutable values have been tampered with. Gen8 raids have this correlation for multiple values. Due to a higher-than-normal amount of CPU calculation required and not wanting to lag the GUI as you flip through boxes, PKHeX does not implement this as a live check -- you must manually check it with other tools/plugins. Gen8 overworld encounters have this correlation for multiple values. Since the seed is constrained to only 32 bits, the calculation is instant, thus done by PKHeX. (raids use a 64 bit seed, thus a 2^32 search space needed). Gen5 mystery gifts that are shiny have a simple correlation for PID. Unmentioned: again, depends on the encounter.