Kaphotics

Use the encounter database. Stop trying to fudge data if you don't know the requirements for the encounter. 1. Should have 4 flawless IVs, not 3. 2. Should have a Dynamax Level of at least 8. 3. Must be ability 1. Changing the PID/EC/IV/Nature for these encounters is traceable, by the way. There's a correlation for Max Lair raids, but its computation is too slow to be done without impacting the program's performance.

Programs don't magically become "smart". It takes time to add features. Old versions of the program don't have all the smarts that a prior version would have. We're skeptical of your memory, because multiple different tools are telling us the data did not originate how you're saying it originated. Programs don't magically become "smart". It takes time to add features. Old versions of the program don't have all the smarts that a prior version would have. If you use cheat codes, don't assume they have no side effect. The game generates data according to patterns, because that's how the game code works. If your data does not follow a pattern, then obviously you did something outside the bounds of normal gameplay (cheats). Again, programs don't become "smart" without effort. Nobody has documented, organized, and codified receivability restrictions for all games.

Read the stickies.

Did you even bother looking at the save file within PKHeX? Literally everything is illegal, so this is a hacked save file for sure.

JERMEY stuff is just wild captures from the game. Literally nothing special besides it was an official cloned PKM. I'm not sure if they've been vetted to RNG conditions being able to encounter the encounterslot with the PIDIV, but I wouldn't be surprised if they were debug-ROM forced encounters (ignoring encounter slot and Method H nature loop).

No. If only there were options in the main window.

You're supposed to beat the 50th trainer afterwards in game.

Problem: Nobody has serialized the event data needed for PKHeX to recognize those gifts.

https://bulbapedia.bulbagarden.net/wiki/Obedience

PKHeX does not provide auto-legality functions, that is a plugin. Update your plugins. Ask for plugin help wherever you found the plugins, not here.

Dev build is fine to use, no real internal changes have been made since the release earlier besides this extra sort setting -- no risk of data corruption. It's stable. I post new releases when the program feels "stable" enough, but I don't want to spam people with update notifications in posting new releases constantly. I don't expect the next "stable" release until September or October, as there really isn't enough being added at this time. Besides bug fixes and small additions, there might be trashbyte legality checks in the future which will take time to fully iron out before being pushed to as a release.

To clarify, after the latest release, I added more settings so that you can have your sorting behavior. The bleeding edge builds have this setting now. Default behavior is not to sort, but you can change it to whatever sorting mode you want.

I've added something to sort the database when it initially loads, via the program settings. Try it out on the bleeding edge build -- https://projectpokemon.org/home/files/file/2445-pkhex-development-build/ The existing logic would sort by the slot identifier string; when viewing dumped pkm files, would be based on the filename. Slots in save files would be named after their box/slot & save file, matching the order in the save file. The new "Identifier" option replicates that behavior. The new "SpeciesForm" will just order by Species->Form->Identifier. I have more than 100k files for my database; sorting them slows down the loading of the database, hence why the default option is disabled. Try to rely on the search options & advanced filters more than visually scrolling

Outside of the PKHeX program is not controlled by PKHeX. You can sort your folders however you want. In Windows's File Explorer, you can click on the column titles to change the sort order.

Refer to the timestamp at the top of PKHeX's window, indicating the version is from May. Palkia was captured in July. Palkia is not a persistently-available Pokémon in GO. PKHeX's database (as of May) does not have any entries for future availability. It's legal with current-date legality databases, which will come in a future PKHeX update (probably in a few hours, actually).

The required .NET Framework version hasn't changed since 2017, so a download from 2018/9 won't really do you any good

Already reported and fixed, will be fine in the next release. https://github.com/kwsch/PKHeX/commit/7ee60d9e98ea6902733e40435c78de1f9e5da876#diff-5f2545732600db97b50b7bc2a2214cbc60c4689ce5a887f144930dae611e52d4

The dumping logic adds in the swarm slots after the base slots are dumped; issue is, there are two "Dark Cave" tables with the same ID, and the "First()" call returns the high-leveled dark cave instead of the low level one where the swarm is present for. https://github.com/kwsch/PKHeX.EncounterSlotDumper/blob/8f3a5ce58f3318fd3a6ce8732d97445f29526df7/Gen4/Dumper4.cs#L292-L298 https://github.com/kwsch/PKHeX.EncounterSlotDumper/blob/8f3a5ce58f3318fd3a6ce8732d97445f29526df7/Gen4/Dumper4.cs#L702-L746 I need to check if there's any other instance where a parent location ID has multiple tables, then ensure that the correct table gets the correct swarm mutations to slot0/1/etc. edit: just marill and dunsparce have multiple tables/location. Need to have a small workaround and redump Resolved on latest commit: https://github.com/kwsch/PKHeX/commit/fc03076093dbafb1bd9741b99d8d3570043aaa82

fixed on latest

Already behaves fine on the latest commits; was fixed before any of this was reported.

PKHeX calculates stats for whatever the regular mainline game stats should be. The game doesn't always store the calculated stats in all formats. For generation 3, boxed PKM data is stored without stats, so withdrawing in-game will cause the game to re-calculate, and depositing via PKHeX will discard whatever stats are calculated. PKHaX exists to skip some user-convenience logic like stat calculation and ability list narrowing. Use responsibly.

Already been reported and fixed. Either wait for the next release or use the dev testing build in the meantime.

Probably not a clean installation (dll should not be present).