Inconsistency in Met Location

[Captain_Tid]

Hi, hope I'm posting this in the right place. I'm new to the community, need a little help to essentially just clarify that I'm doing things correctly. I'll try and be concise but there's a few moving parts here, so bear with me.

I'm using PKHeX to restore some mons I sadly lost when my Scarlet save data was wiped. Luckily the mons in question were all from Sun or earlier, so my plan is to just recreate them in my Sun save file and then use Poke Transporter to restore them to Home.

 

As is probably well known, there's an issue with the way Sun/Moon clears data out of the Resort. Due to this, you can use the 'Dump Box' feature in PKHex on a Sun save file and get a CSV with seemingly all of the Pokemon you previously had in your boxes, even if you've since used Poke Transporter to move them into home. This is really lucky for me, since it gives me a way of accessing the data of all the mons who I'm trying to recreate.

 

 

In this screenshot for instance, none of these pokemon are actually in my boxes in my Sun save file, and I can't access them looking through the boxes in PKHex either. They just exist as ghost data from when they were loaded into the resort.

My issue is that when I try to recreate the data as it is listed in this CSV, PKHex flags it as illegal. The Golem I have highlighted in the screenshot, his MetLoc in the csv is 'a link Trade (NPC)', and his origin game is Platinum. When I set those parameters in pkhex, though, I get this error:


But it can't be invalid. Because it's the data that is apparently stored by my original, totally unmodified and legit, save file from Pokemon Sun.

 

So what I'm ultimately asking is, am I misunderstanding some part of this, or is there a mistake in the legality checker here, such that it believes data is illegal when it isn't? I hope this all makes sense. Please ask away if I can provide more clarifying info. Thank you!

[theSLAYER]

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?

[Captain_Tid]

No, I didn't. This is the first time I've modified any of my save files in any way, beyond official software for trading up Pokemon.

 

I can't easily share a table in a post, so I've just chucked the header and golem's line into a drive document quickly:

https://docs.google.com/spreadsheets/d/1w5rZWXE2lzx3YrqsfBXkkWQv3sJLoQNmjolpLxX1m1A/edit?usp=sharing

[theSLAYER]

19 minutes ago, Captain_Tid said:

No, I didn't. This is the first time I've modified any of my save files in any way, beyond official software for trading up Pokemon.

 

I can't easily share a table in a post, so I've just chucked the header and golem's line into a drive document quickly:

https://docs.google.com/spreadsheets/d/1w5rZWXE2lzx3YrqsfBXkkWQv3sJLoQNmjolpLxX1m1A/edit?usp=sharing

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.

[Captain_Tid]

Thank you so much for responding so quickly and helping resolve this!

Do you mind if I ask as well, when I'm saving these Pokemon as .pk7s, the file name that is automatically generated doesn't match the one that the CSV is reporting.

For instance, Golem - EDE9DAF9D8AC.pk7 is what's listed in the csv, but the one I've recreated is saved as Golem - 6DB0DAF9D8AC.pk7

I can see the back half is accurate, which seems to just be the PID. But the 'EDE9'is being replaced with '6DB0'. Is that a reflection that I'm missing some key part of the recreation?

[Kaphotics]

It's a checksum of the data.

[Captain_Tid]

Sure, so it being different indicates that there are parts that do not match the original data. But not necessarily that there's an issue that would mark the Pokemon as being illegitimate/illegal?

[Kaphotics]

A checksum is a checksum, nothing more. In this case, it's a quick indicator that the data is not the exact same as the other file.