theSLAYER

So hyper training sets a flag (for each stat) on the Mon, so that games know it’s an hyper trained stat (so that games can display the perfect stat), and the flag is retained in HOME transfers.

Just use mints for nature, and hyper training for IVs. It would do you good to be suspicious of any flawless legendaries you receive/find, as those, are likely hacked. (they are possible to obtain, but what are the chances of them being shiny and perfect?)

At your own risk.

1. I don't remember what the value should be, and 2. I think they *do* undergo regrowth cycle, if ignored for too long.

Uploading fixes now, cheers

(Maybe I used the wrong save or it was added in a new revision, but I didn’t see it in my save of the other tab on the current PKHeX revision. Or maybe it didn’t show the slots cause my resort could have been empty? It’s an old save so I don’t remember clearly. In any case, I’ll download the latest and check again >< thanks for helping them) So far HOME doesn’t ban for duplicates, and don’t seem to apply action for that. FYI any bans or actions so far: The banned HOME accounts were related to targeted individuals who were buying and selling via using HOME as a platform to complete the transaction. Eternal Bad eggs occurred for those who brought up hacked Eternal Flower Flower (caught in XY); transformation was species+form based, not targeted; suggests it was more to block Eternal flower Floette, rather than a targeted strike against users. HOME previously blocked entry for duplicates of a HOME tracker (is was due to the tracker, not because of the regular details), but trackerless duplicates enter just fine. They’ve since allowed for tracker duplicates now (gets reassigned a tracker); this suggests it was more of a technical issue caused by an assumption they had, rather than actual action Granted, they keep a log for every piece of detail, but they’ve not taken action.

And a change in any data can influence the checksum. Anyhow, since I do not know how to extract Resort data from PKHeX, I'll recommend something else: This may work, even if you're using a save as opposed to a ram dump.

Okay I figured it out. When you Poké transfer a Pokémon into Gen 5, it is assigned the met location ID 0x30001. That number for Met Location then doesn't get modified as a mon is transferred further up. (read Gen 5 ID list here) The CSV generated by PKHeX apparently didn't take that into account; it took the ID and displayed a name based on Gen 7 locations, which would be link trade (read Gen 7 ID list here) So it is merely a display issue (I asked about PKSM cause it had display issues for some transfers and it reminded me of that). In any case, fixing the Met Location to what PKHeX suggests would fix the issue.

Did you previously use PKSM or some other third party app to shift the Golem up into Gen 7? Also, are you sure it was met location you're looking at? what does the full line for Golem in that CSV look like?

legal only if you match all details, such as encounter slot. When we talk about encounter slot, an example is to imagine a table with all the possible grass encounters for a route. It is possible for the encounter slot for your PIDIV, relates to a different encounter (could also be different species).

Probably related to some PKHeX.Core change, will look into it later

Left if the favourite mark that is applied in LGPE when you favourite a mon. (Honestly I don’t know if you can apply it in other games; I assume there might be a similar feature hence why it’s still there) The right is the “Battle Ready” symbol, only used in SWSH. It is basically retired in other games, as HOME now wipes moveset and assigns game specific moveset, when a Mon a transferred to another game outside of SWSH

We don’t work with state saves. importing state saves that aren’t related to your save would cause it to fail.