"Final terminator missing'' Shiny Mew from Faraway Island Island Event

[D3ViL02]

I've RNG manipulated a Shiny Mew using MGBA Emulator and then moved it to my physical copy of Emerald, I was using the previous version of PKhex and it would be flagged as Legit, but now after updating to the 260320 Version it now gets flagged as Invalid. Should I get worried ? If I move it to Platinum for example it gets flagged as Legit tho.

[Kaphotics]

3 hours ago, D3ViL02 said:

I've RNG manipulated a Shiny Mew using MGBA Emulator and then moved it to my physical copy of Emerald, I was using the previous version of PKhex and it would be flagged as Legit, but now after updating to the 260320 Version it now gets flagged as Invalid. Should I get worried ? If I move it to Platinum for example it gets flagged as Legit tho.

Probably because you used a not-Japanese save file to catch it, thus having invalid trash bytes applied. Program working as intended.

The Gen3=>Gen4 transfer re-encodes both Nickname and OT, so the original trash bytes are not carried forward, hence the clean report in Gen4.

[D3ViL02]

Wow, thanks for the clarification, I used a file from an old playthrough. Is it safe to transfer this Mew ? Or should I play Emerald again in Japanese and get the Mew ?

Edited March 30 by D3ViL02

[AlamosIT]

I noticed the same thing happening in my gen III save files with a few mons obtained by trade a lot of years ago.

For example, I have this Crobat since 2007, obtained from a kid that had a English copy of Emerald (we traded mons with my Italian one).

What could have happened?

0169 - CROBAT - DD3BCF68A15E.pk3

[Red531]

It flagged a pokemon that I caught recently. Half my pokemon (most that i have never touched) seem to have an issue, the other half seem fine. What parameters are actually important for the check? Should all pokemon caught within a game have the same trash bytes?

Pidgey_52622CBA.pk3

[AlamosIT]

3 hours ago, Red531 said:

It flagged a pokemon that I caught recently. Half my pokemon (most that i have never touched) seem to have an issue, the other half seem fine. What parameters are actually important for the check? Should all pokemon caught within a game have the same trash bytes?

Pidgey_52622CBA.pk3 100 B · 2 downloads

Did you use an emulator or an actual copy?

[Red531]

On 3/31/2026 at 1:35 AM, AlamosIT said:

Did you use an emulator or an actual copy?

emulator

[AlamosIT]

11 hours ago, Red531 said:

emulator

Maybe some emulators don't create a 1:1 actual-like save file, so there could be some issues in "trash bytes".

Maybe, in my case, that Crobat came from an old bootleg copy and other mons I have could come from emulator (shiny mons probably obtained with RNG manipulation).

@Kaphotics could this be a correct explanation?

Is there a way to "clean" these Pokémons?

[AlamosIT]

@D3ViL02 @Red531 I was looking here, and maybe I found a way to clean these mons.

Do Ctrl+Click on the OT name and write FF in $05 and $06 slot, this worked for me

[AlamosIT]

With new PKHeX version (20260505), old "illegal" mons are now legal... 

Edited May 25 by AlamosIT

[roxas7234]

On 4/14/2026 at 7:35 AM, AlamosIT said:

@D3ViL02 @Red531 I was looking here, and maybe I found a way to clean these mons.

Do Ctrl+Click on the OT name and write FF in $05 and $06 slot, this worked for me

Not sure if there is a batch fix, but doing this manually to everything effected worked for me.

 

I was having this issue and was scratching my head because I've always played on cartridges and was only getting the error on some old mons, but anything I caught recently was fine.

Looks like it was caused by using the batch editor to change your Pokemon OT, the blank name bytes weren't applied if your new name is shorter so you get the invalid termination error. I did this a few years ago, so the batch editor may not cause this issue anymore.

 

I'm using my childhood save, and I changed it at some point to my real name instead of something I wrote when I was 10.