HappyMaractus

Thank you.

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.

In Gen III/IV, certain Pokemon can have different sizes based on calculations made using their Personality Value and IVs. The equations are on the Personality value article of Bulbapedia, in the section on Size. But PKHeX doesn't seem to do these calculations/provide the results of the calculations. I did try to make a calculator for this myself yesterday, but the last time I coded before that was half a decade ago and I was never any good to begin with, so the resulting program...I wouldn't trust my program. Anyway, I'd like to request a way to know the s value, as seen in the Bulbapedia article I mentioned. for the currently displayed PKM. Taking the s value and doing the rest of the calculations isn't hard, but getting the s value is very hard. If you can provide further info than that then that'd be cool too, but the s value might still be important too in case it could influence the size of pokemon imported from Gen III/IV to Gen IX's new size system. (Having to reverse the final calculation to find s to figure out if the pokemon is large/small enough to get a Jumbo/Mini Mark is not something I would want to have to do repeatedly, assuming it even works like that.)