Bug: XD Met Locations Not Being Read Correctly From .gci Save File

[HappyMaractus]

I just opened my Pokemon XD .gci save file (which I copied to an SD card using GCMM on a Homebrewed Wii and then transferred to my PC) using PKHeX to have a look at the exact stats of my 'mons there but found that PKHeX isn't reading the Met Locations Correctly when loading the save. For example, I have an Arbok that my copy of XD correctly tells me I met in the Cipher Key Lair. However, when I load my save into PKHeX and look at that exact same Arbok I find that PKHeX says that Arbok's Met Location is Victory Road (RSE). Or, for another example, my starter Eevee (which is supposed to have a Met Location of "Obtained from [protag's] Dad") has a Met Location of Littleroot Town. Or the Houndoom from Cipher Lab being reported as met in Fortree City. And so on. Not a single Met Location seems to have been accurately read by PKHeX from the save file.

No idea if PKHeX will save the data correctly or change the Met Locations to what it's showing me, and honestly I'm a bit fearful of trying to find out. (Though I guess if I had some reassurance of how to check safely I could do so to help diagnose the problem if needed.)

I won't venture a guess as to what exactly is the cause, but I'm pretty sure it's a bug with PKHeX of some sort. (I did try to find any other reports of this happening, but I could only find people saying they couldn't open their gci save files with PKHeX.) So yeah, I am reporting that PHeX seems to have a Bug with reading the Met Location of Pokemon in XD save files.

Also, tho I doubt it's a big deal, should the CurrentRegion value in the Block Editor be reporting PAL even though I'm in USA and thus NTSC_U? The OriginalRegion value says NTSC_U though.

[Atrius97]

This issue has already been fixed in the latest dev build of PKHeX, met location text should appear correctly in future releases of PKHeX.

[HappyMaractus]

Thank you.