PKHeX new update legality errors (contribution page)

[mcw4v3-x]

49 minutes ago, Kaphotics said:

Still unable to replicate. Did you disable Legality.Tradeback.AllowGen1Tradeback in settings?

No I did not.

[Kaphotics]

Without seeing a screenshot of what you see, it is impossible to figure out what you have wrong.

[mcw4v3-x]

[Kaphotics]

7 hours ago, mcw4v3-x said:

As per the first post in this thread:

Quote

NOT FOR USER MISTAKES OR TROUBLESHOOTING HELP.

I had reminded you this two years ago with your previous false report.

I am 99.9999% sure you've attempted to hack in the 'mons rather than present your legitimately obtained as examples of the legality checker not working.

There are multiple failing features present in your screenshot that are indicative of cheating:

1. Having maxed EVs at a very low level. While not impossible (due to Daycare resetting back to the current level's 0% threshold), I highly doubt you painstakingly did this.

2. Having maxed IVs. I really doubt you abused the RNG to get a perfect IV spread.

3. Catch Rate of 0, indicative that you traded it to Gen2 and removed the item, and traded it back. Highly unlikely you did that, and instead just forgot to manually enter the untouched catch rate when generating it.

4. Finally, the fatal flaw: In-game trades do not store the actual Trainer name in the OT field. They use a special 1-character string to tell the game to display the localized variant of "TRAINER". PKHeX is rightfully flagging that the OT name has been altered, because it does not match what the OT name should be.

[roxas7234]

Hi,

For some reason my Rayquaza I caught during the shiny event in Scarlet last year is still marked as illegal.

Initially I thought it was just because the event database hadn't been updated yet, but noticed now almost a year later its still appearing as illegal.

Adding one into the box from the encounter database is marked as legal, so not sure whats causing it.

 

This mon is 100% legally caught and unmodified. Leveling, hypertraining and EVs were done in-game.

0384 ★ - Rayquaza - 0FE4DD137505.pk9

[Kaphotics]

2 hours ago, roxas7234 said:

Hi,

For some reason my Rayquaza I caught during the shiny event in Scarlet last year is still marked as illegal.

Initially I thought it was just because the event database hadn't been updated yet, but noticed now almost a year later its still appearing as illegal.

Adding one into the box from the encounter database is marked as legal, so not sure whats causing it.

 

This mon is 100% legally caught and unmodified. Leveling, hypertraining and EVs were done in-game.

0384 ★ - Rayquaza - 0FE4DD137505.pk9 344 B · 3 downloads

Doubtful; the RNG seed does not yield the PID/IV that you have on the file, indicating that something was modified (such as the Encryption Constant).

[TiffanyDarlet]

54 minutes ago, Kaphotics said:

Doubtful; the RNG seed does not yield the PID/IV that you have on the file, indicating that something was modified (such as the Encryption Constant).

One of the old pkhex, when legends Z-A released some of my shiny ultrabeast appeared as illegal and modified in pkhex, but in the next build it fixed, if they use a old pkhex build they can compare if still appears as legal or no

[roxas7234]

7 hours ago, Kaphotics said:

Doubtful; the RNG seed does not yield the PID/IV that you have on the file, indicating that something was modified (such as the Encryption Constant).

That's really odd, I am certain I've never modified it.

Anyway,

Thanks for having a look!

[Rubino]

Hi, this litte friend is still not legal.

 

0006 - Charizard - 3B7F45A5D41C.pa9

[sora10pls]

31 minutes ago, Rubino said:

Hi, this litte friend is still not legal.

 

0006 - Charizard - 3B7F45A5D41C.pa9 344 B · 1 download

This Charizard is illegal.

The Kanto starter you're given from that side mission comes with the met location ID 30027, yours has 103.

[Rubino]

On 12/23/2025 at 2:17 PM, sora10pls said:

This Charizard is illegal.

The Kanto starter you're given from that side mission comes with the met location ID 30027, yours has 103.

thanks, I only boost him iv and ev, dunno what happened.

How can i fix him?

Edited January 4 by Rubino

[theSLAYER]

1 hour ago, Rubino said:

thanks, I only boost him iv and ev, dunno what happened.

How can i fix him?

As mentioned ID is wrong. Also IV boosting incorrectly can cause hacks, this thread isn’t for helping you with hacks.

[Asia81]

Meltan and Hoopa-Unbood are flagged illegal in my save.
I didn't touch them at all, except for Hoopa I changed his form in-game with its own item and that's all.

0720-01 - Hoopa - F92BC278F568.pa9 0808 - Meltan - 01F63FC0C102.pa9

[Kaphotics]

2 hours ago, Asia81 said:

Meltan and Hoopa-Unbood are flagged illegal in my save.
I didn't touch them at all, except for Hoopa I changed his form in-game with its own item and that's all.

0720-01 - Hoopa - F92BC278F568.pa9 344 B · 0 downloads 0808 - Meltan - 01F63FC0C102.pa9 344 B · 0 downloads

Meltan: fixed shortly after the previous release: Update EncounterStatic9a.cs · kwsch/PKHeX@61a13fd

Hoopa: fixed just now, thanks for the reminder: Misc tweaks for Hoopa-1 plus flags · kwsch/PKHeX@85abb48

[Rubino]

14 hours ago, theSLAYER said:

As mentioned ID is wrong. Also IV boosting incorrectly can cause hacks, this thread isn’t for helping you with hacks.

As I already told, is a legitimate charmender. I maxed iv and ev (in both correct way) to 20 pokemon in za, only this charizard give me unlegit. Is the charmender from the quest, is legit in theory.  I only maxed him ev and iv. How can i fix him, i mean make him legit like he deserve ? Thanks

[Kaphotics]

2 hours ago, Rubino said:

As I already told, is a legitimate charmender. I maxed iv and ev (in both correct way) to 20 pokemon in za, only this charizard give me unlegit. Is the charmender from the quest, is legit in theory.  I only maxed him ev and iv. How can i fix him, i mean make him legit like he deserve ? Thanks

Read the first post of this thread. This thread is not for help when you've made edits to a Pokemon with the program, it is for legitimate things being flagged incorrectly. Z-A has RNG correlations and you cannot modify IVs without invalidating the PID IV+ correlation.

[pokeknight]

The latest version of PKHeX incorrectly marks Apricorn balls as legal for Pokemon with a ChainShiny PID-type caught in Platinum.

[ATRociousFuBear]

Hello! This might be odd as it is not reporting a legality error itself, but something that I believe should be one.

In Legends Z-A (and possibly also Legends Arceus), Alphas all seem to be locked at Scale 255. I've run my own legitimately captured Alphas through PKHeX to double-check, as well as some examples from the encounter table. Before I had learned how to use the encounter table, however, I had altered a legitimately captured non-Alpha Hisuian Goodra to become Alpha since I had struggled for hours to capture an Alpha legitimately. After a few hours of playing, I had noticed that its size was showing incorrectly within the game's stat screen despite the Goodra being recognized as being an Alpha. After looking over the file again, I saw that the Scale had not been altered from what the original Goodra's size was. The stat screen showed M instead of XL but the Alpha marker was still present.

To demonstrate, here is an Alpha Pikachu that I pulled off the encounter table using the most recent software version. After reducing the Scale from 255 (XL) to 0 (XS), it still shows up as being perfectly legal even though it should not be a legitimate encounter. I'm not sure if this is really an issue or if it's something that can be adjusted, but I did want to bring it to someone's attention since I do appreciate all the hard work that has gone into PKHeX! (And I'm also grateful to have learned how to utilize the encounter table! )

Edited 9 hours ago by ATRociousFuBear

[Kaphotics]

2 hours ago, ATRociousFuBear said:

Hello! This might be odd as it is not reporting a legality error itself, but something that I believe should be one.

In Legends Z-A (and possibly also Legends Arceus), Alphas all seem to be locked at Scale 255. I've run my own legitimately captured Alphas through PKHeX to double-check, as well as some examples from the encounter table. Before I had learned how to use the encounter table, however, I had altered a legitimately captured non-Alpha Hisuian Goodra to become Alpha since I had struggled for hours to capture an Alpha legitimately. After a few hours of playing, I had noticed that its size was showing incorrectly within the game's stat screen despite the Goodra being recognized as being an Alpha. After looking over the file again, I saw that the Scale had not been altered from what the original Goodra's size was. The stat screen showed M instead of XL but the Alpha marker was still present.

To demonstrate, here is an Alpha Pikachu that I pulled off the encounter table using the most recent software version. After reducing the Scale from 255 (XL) to 0 (XS), it still shows up as being perfectly legal even though it should not be a legitimate encounter. I'm not sure if this is really an issue or if it's something that can be adjusted, but I did want to bring it to someone's attention since I do appreciate all the hard work that has gone into PKHeX! (And I'm also grateful to have learned how to utilize the encounter table! )

Thanks, fixed on latest commit: Enhance H/W/S invalid messages, flag !255 alphas · kwsch/PKHeX@3a8bc58

On 1/9/2026 at 4:09 PM, pokeknight said:

The latest version of PKHeX incorrectly marks Apricorn balls as legal for Pokemon with a ChainShiny PID-type caught in Platinum.

Thanks, it's actually a GUI bug the invalid Ball you picked is actually being forced back to Poke, but it displayed whatever you selected instead. If you set it to a slot then re-view it, you can confirm the "fixing" of the GUI indication as it really is legal. I've added some logic to display the actual sanitized value (not the selection, if it was impossible), as well as added some logic to check for a specific case where the batch editor/external code managed to set an invalid BallHGSS value.

Add Gen4 HG/SS ball check · kwsch/PKHeX@6e48294