Jump to content

Recommended Posts

Posted (edited)

Here's a fun one, this Togetic is the gift Togepi Egg from Resort Gorgeous, but I traded it from my FireRed to my Emerald before it hatched to get that friendship boost from hatched Pokémon. I'm not sure what's causing it to be flagged as invalid.

 

image.thumb.png.32ab6980870fa85ae5a7172929ac1499.png

Edited by Booster137
  • 4 weeks later...
Posted

Hey, think I've found a bug with the new build of PKHeX. Some of my Pokémon are showing up as illegal in the boxes yet are perfectly legal on the left-hand side. They were caught a few hours ago on Pokémon Sun, very clean. Last major update (back in November) did not have this issue. 

The only edit made to the save between beginning of the game to current is the 3DS's location data. I don't know if that's causing the issues but worth mentioning if it helps you find the bug.

Thank you for all the hard work you do on PKHeX. ❤️

a109aeb30475c4e2424873e7f5d35205.png

main

Posted
3 hours ago, Crazylegs23 said:

It wasnt a hacked raid 

Well, it's not legitimate, it's illegal. The program is working as intended.

This thread is for reporting unmodified-game Pokemon; having any cheat codes active or modifying something to be shiny is not legitimate.

Posted

Hi, I would like to report some issues as I was trying latest dev build:
- The new "naming screen->TID/SID frame pattern" check is working as expected but is not verifying your Eevee starter. It's shown legal even with an impossible TID/SID combo.

- It may be caused by these changes or something else, but drag & dropping Colo/XD files into the app makes "Met Location" show places from R/S/E/FRLG. When you hover over any pkm, the tooltip shows the right one. Legality window too. Restarting the program and opening the save from File>Open fixes it.

Posted

Hello,

I'm reporting an issue regarding the 3 Alpha Pokémon found in each of the Lake Guardians' caves (story-related): Hisuian Goodra, Hisuian Zoroark and Overqwil.

Having multiple save files, I noticed that upon capture, the legality check is fine.
However, after transferring them back and forth through Pokémon Home, they appear as illegal.

After comparing, I realized that the base height, weight, and scale are set to 127 right after capture.
But after the transfer with Pokémon Home, they change to 255, and the Alpha mark appears.
PkHex is unable to match the encounter due to the weight change and the addition of the Alpha mark and flag.

Since their capture, these Pokémon have been placed in storage and have not been altered in any way, aside from the transfer to Home.
The test was just redone with all 3 clean Pokémon.

Hopefully this isn't a duplicate if the issue has already been reported.

image.thumb.png.0d279dd8327f1de9c64053ce44ae2fa6.png

0571-01 - Zoroark captured - 15D8A5243C31.pa8 0706-01 - Muplodocus captured - 5884409E22D2.pa8 0904 - Qwilpik captured - A082A9791F34.pa8 0571-01 - Zoroark Home - 5663A5243C31.pa8 0706-01 - Muplodocus Home - 9AB1409E22D2.pa8 0904 - Qwilpik Home - E8BBA9791F34.pa8

Posted
1 hour ago, Yorhu said:

Hello,

I'm reporting an issue regarding the 3 Alpha Pokémon found in each of the Lake Guardians' caves (story-related): Hisuian Goodra, Hisuian Zoroark and Overqwil.

Having multiple save files, I noticed that upon capture, the legality check is fine.
However, after transferring them back and forth through Pokémon Home, they appear as illegal.

After comparing, I realized that the base height, weight, and scale are set to 127 right after capture.
But after the transfer with Pokémon Home, they change to 255, and the Alpha mark appears.
PkHex is unable to match the encounter due to the weight change and the addition of the Alpha mark and flag.

Since their capture, these Pokémon have been placed in storage and have not been altered in any way, aside from the transfer to Home.
The test was just redone with all 3 clean Pokémon.

Hopefully this isn't a duplicate if the issue has already been reported.

image.thumb.png.0d279dd8327f1de9c64053ce44ae2fa6.png

0571-01 - Zoroark captured - 15D8A5243C31.pa8 376 B · 0 downloads 0706-01 - Muplodocus captured - 5884409E22D2.pa8 376 B · 0 downloads 0904 - Qwilpik captured - A082A9791F34.pa8 376 B · 0 downloads 0571-01 - Zoroark Home - 5663A5243C31.pa8 376 B · 0 downloads 0706-01 - Muplodocus Home - 9AB1409E22D2.pa8 376 B · 0 downloads 0904 - Qwilpik Home - E8BBA9791F34.pa8 376 B · 0 downloads

Thanks, fixed on latest commit:

https://github.com/kwsch/PKHeX/commit/ca03311d212a7ef395a674fe8eaec6634e76a757

  • 3 weeks later...
Posted

Hello,

PKHeX marks like invalid the Met location where I found my Xatu legally in Pokémon Sword.

It was on a raid in the Wild Area.

image.thumb.png.4dde400ad81bf8b80fd0f3f1cf35f7c0.png

Posted
On 2/3/2025 at 6:52 AM, Kaphotics said:

Working as intended. You don't have a `trainers` folder with data for BD or SP, so the program has to generate it with some kind of trainer data. The only trainer data available is your currently loaded save file, so it uses that. Since a BD/SP encounter cannot be handled via the Original Trainer in sw/sh (an entirely different version), the program flags it as illegal.

You need to either provide `trainer` pkm files so that the encounter database can generate encounters with "legal" trainer data, or you need to change the trainer data of the resulting pkm after it has been generated with placeholder values. It's not really advisable to have the program create a random trainer for the "other" games it has no trainer data for, as there are pros & cons of doing it vs not.

The "mew" and "jirachi" obtained in the regular game process will show the problem "Invalid: Invalid Current handler value, trainer details for save file expected another value." Is this because the game program runs like this? (I know that it can be solved by simply changing "HT" to "OT". At the same time, in livehex, "current handler" is displayed as "OT" and there is no "latest handler information")

Posted
11 minutes ago, Dybala said:

The "mew" and "jirachi" obtained in the regular game process will show the problem "Invalid: Invalid Current handler value, trainer details for save file expected another value." Is this because the game program runs like this? (I know that it can be solved by simply changing "HT" to "OT". At the same time, in livehex, "current handler" is displayed as "OT" and there is no "latest handler information")

Not really relevant to this thread; a Pokémon that is present on SaveFile "A" must have the correct handler state in that if it originated from the save file, it is handled by the OT, otherwise, it be handled by the HT. Plugins that just read data directly from RAM and display it on a different/blank save file are obviously not the same save file that it was read from, hence the mismatch.

  • 4 weeks later...
Posted (edited)

I noticed a peculiarity related to Pokémon obtained as part of the Japanese Gather More Pokémon! Campaign

Prior to 24.11.11, the PID type in this example using Cyndaquil (attached photos) was noted as BACD_R.

Post-24.11.11 update, the PID type is BACD [BACD_U_AX]. I am still working on my understanding of PID types in gen 3, but is this accurate and intentional?

My guess is that the origin seed in this example (0000BCFE) appears in both BACD_R and BACD_U_AX, and PKHeX isn't distinguishing between the two and defaulting to the latter?

The attached photos include the encounter/PID type and errors for the same Pokémon from the 24.07.27 and 25.02.23 releases of PKHeX. The sample save file I'm using can be found here

This is my first forum post, so if this is better suited somewhere else I apologize.

24.07.27_error.png

24.07.27_pkm.png

25.02.23_error.png

25.02.23_pkm.png

Edited by mxrvine
Original post was very verbose. Tried to cut down content based on what I've found online since posting that answers some of my own questions.
Posted

A 16 bit seed, like 0xBCFE, is also a 32 bit seed, 0x0000BCFE.

Detection was added in October-2024, which explains why the "was this ever contributed" from July-2024 is no longer flagging, and the encounter is better matched.

The BACD_U_AX means: set the two halves of PID with calls A and B in reverse order (B, A), which is different from Method 1/2/4 (A, B). Then IVs are set.

BACD is the call order, `U` is "unrestricted", meaning it can be any 32-bit seed (well, not entirely), and AX means it has "antishiny xor" behavior when creating the PID, with special restrictions on the A call result. The "A" call gets truncated and is xored with the trainer ID and B to ensure it is never shiny.

It's still flagged because the seed 0x0000BCFE is not a valid starting seed to generate the Pokémon.

 

  • Thanks 1
  • 3 weeks later...
Posted
2 hours ago, Radd said:

image.png.b5e83fb386acbd0bfc3e1ef75ef7ed5d.png
image.png.1d464032983cd0047e67cf9e7d40ee04.png
I apologize if I am incorrectly reporting a bug.  I am playing on a vanilla copy of Pokemon Colosseum on Dolphin.  Its saying this TID is impossible, if this isn't a bug I am assuming its because I am playing on Dolphin.0156 - QUILAVA - 41BABB9D2951.ck3

01-GC6E-pokemon_colosseum.gci 384.06 kB · 0 downloads

Works fine on latest commit.

https://github.com/kwsch/PKHeX/commit/87d55fc303d599181ad2e614acae5765c3df173e

Posted (edited)

Hi,

Noticed an issue/bug and while i see its been mentioned above as working on the latest version/commit, I am on the latest version and it still giving the issue/bug.

Seams all Pokemon caught in Pokemon XD are showing as "Invalid: Trainer ID is not obtainable from any RNG seed" but not my starter Eevee.

It was played via emulator (Dolphin iOS Fork) if that is the cause for this? No cheats were used during my game play.

If you need anything else to help let me know, happy to share my save file or any of the Pokemon :)

Screenshot 2025-06-05 at 10.10.16 am.png

Screenshot 2025-06-05 at 10.12.04 am.png

Screenshot 2025-06-05 at 10.19.31 am.png

Edited by KarlosTheJackal
Posted
3 hours ago, KarlosTheJackal said:

Hi,

Noticed an issue/bug and while i see its been mentioned above as working on the latest version/commit, I am on the latest version and it still giving the issue/bug.

Seams all Pokemon caught in Pokemon XD are showing as "Invalid: Trainer ID is not obtainable from any RNG seed" but not my starter Eevee.

It was played via emulator (Dolphin iOS Fork) if that is the cause for this? No cheats were used during my game play.

If you need anything else to help let me know, happy to share my save file or any of the Pokemon :)

Screenshot 2025-06-05 at 10.10.16 am.png

Screenshot 2025-06-05 at 10.12.04 am.png

Screenshot 2025-06-05 at 10.19.31 am.png

Read the message directly above yours. Test on the development build to see the latest commits with all changes since the last release.

Posted
8 minutes ago, Kaphotics said:

Read the message directly above yours. Test on the development build to see the latest commits with all changes since the last release.

Ohh is the development build different from the latest version? If thats the case would explain my miss-understanding! haha

I'm not 100% sure how to get the latest development build but ill work it out and test it, thank you :)

Posted

Porygon2 from a CHS language SwSh game is showing the wrong default nickname. I'm testing with VGC20 Porygon2 and the latest release. Pictures are from previous release but it happens in latest release too.

My self-redeemed Porygon2 looks like this:

4d5Djup.png

And I have video proof redeeming this Porygon2, which also shows the same nickname in the video:

Spoiler

 

When testing the wondercard, it shows a different nickname:

Spoiler

0dY0ao8.png

Checked the Encounter Database and they all have the same nickname as the second screenshot. The wondercard page for VGC20 Porygon2 says it should have default nickname, so the first screenshot should be the default nickname.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...