Poketransfer Pokémon PID mismatch

[Cecillia]

Hello,

 

I found an issue with PKHeX, which I will explain, I found this specific issue only being there with Pokémon transferred to BW/B2W2 from Gen III, including Colosseum/XD, (sent to Gen IV prior) and Gen IV games, which are afterwards sent to Bank.

Let's say I caught a Mismagius in Pearl, and transferred it over to BW/B2W2, the met location will be "Poké Transfer", but the original game still is Pearl. This causes it to show an Encounter PID mismatch, even though the PID should check out. View the next screenshots for the error. 

 

I don't know if this is normal, but I thought it was odd to say the very least.

 

Kind regards,

Cecillia

[theSLAYER]

Hi @Cecillia, based on my experience with dealing with reports for this, this is highly likely not a bug.


The RNG procedure for Pokemon Generations 3&4 are well understood,
and based on that, it is understood that PID, IVs and nature and encounter details are linked.

The message you get means the Pokemon is hacked.
(example, one or more of the factors mentioned above are not linked properly)

To see a more detailed legality analysis, hold down the "Control" button on your keyboard, while clicking the red exclamation mark.

This page here will show some details to resolve certain parts of PID mismatch, using RNG reporter.
AFAIK creators of PKHeX does not intend to auto-fix PID mismatch problems, since there are existing tools out there that users can use,
and it'll not be a good use of time.

 

If you have any doubts, upload the pokemon files in the next file and someone will have a look at em.

[Cecillia]

Alright thanks for the information, I'll try to check if I can fix it. I appreciate it that you took time to answer my question. And here is the Pokémon detailed info:

 

Invalid: Encounter Type PID mismatch.
===

Valid Move 1: Learned by Level-up.
Valid Move 2: Learned by Level-up.
Valid Move 3: Learned by Level-up.
Valid Move 4: Learned by Level-up.
Valid Relearn Move 1: Valid.
Valid Relearn Move 2: Valid.
Valid Relearn Move 3: Valid.
Valid Relearn Move 4: Valid.

Valid: Valid Wild Encounter at location.
Valid: Nickname matches species name.
Valid: Current level is not below met level.
Valid: All ribbons accounted for.
Valid: Ability matches ability number.
Valid: Correct ball for encounter type.
Valid: Gender matches PID.
Valid: Nature matches PID.
Valid: History block is valid.
Valid: Geolocation: Country is in 3DS region.
===

Encounter Type: Wild Encounter Grass (Misdreavus)
PID Type: None

Anyway, some of my Pokémon were automatically correct, others needed some rerolls... Here is the Mismagius, if it's hacked I'll try to correct it.

 

429 - Mismagius - A4378ABCECCA.pk7

[Ruby Genseki]

Due to the PID type, the easiest way to solve your issue seems to be making it look hatched:

Though, if you wanna make it a wild encounter in order to keep the Great Ball (as a gen 4 hatched Pokémon can only be in a regular Ball), you can use RNGReporter and generate a new PID. IIRC, the gen 4 wild PID method is the default one (Method 1).
Anyway, here's the corrected file: 429 - Mismagius - D40F8ABCECCA.pk7

[Cecillia]

I got some other mons left as well, I corrected some myself.

[Ruby Genseki]

Which ones do you have left? If there are any that you're unable to correct yourself, as theSLAYER said, upload the files.
And, as a tip, if you're making some other Mon look hatched, make sure the "Egg received" date is not more recent than the hatched/transferred date. A mismatch like that doesn't necessarily make'em illegal, but still looks fishy and I've seen many people overlooking it.

[Cecillia]

OK, I got some legendaries left, also I came across a real bug this time.

[Ruby Genseki]

3 minutes ago, Cecillia said:

I got some legendaries left

Well...legendaries cannot look hatched since that'd make'em illegal anyway xD

3 minutes ago, Cecillia said:

also I came across a real bug this time

What is it? can you upload a screenshot or something?

[Cecillia]

Sure, here's the screenshot:

 

[Kaphotics]

Profanity filter tripping for the OT.

[Ruby Genseki]

8 minutes ago, Cecillia said:

Er...well...Idk what to say about this one. All the Victinis I have are all right, so there must be something wrong with that one of yours. Could you send me that file to give it a look?

EDIT: Yeah, what Kaphotics said seems plausible. Did you check it?

Edited November 6, 2017 by Ruby Genseki

[Cecillia]

2 minutes ago, Ruby Genseki said:

Er...well...Idk what to say about this one. All the Victinis I have are all right, so there must be something wrong with that one of yours. Could you send me that file to give it a look?

EDIT: Yeah, what Kaphotics said seems plausible. Did you check it?

 

It is indeed a filter tripping for OT. Here is the PK7 anyway.

494 - Victini - BEBC60C05A92.pk7

[Ruby Genseki]

When the OT name is banned from gen 6 onwards, it is automatically changed for a generic one. Since this Victini comes from White, PokéBank would have its OT renamed as "Shiro*".

Though, since you're using PKHeX anyway, change it however you want. As far as I know GF's legality filters don't take trash bytes into account.

Edited November 6, 2017 by Ruby Genseki

[Cecillia]

Alright, anyway AFAIK the games don't see incorrect PIDs as incorrect, at least not in <= SuMo. I can't say anything about USUM.

[Ruby Genseki]

3 minutes ago, Cecillia said:

Alright, anyway AFAIK the games don't see incorrect PIDs as incorrect, at least not in SuMo.

What do you mean? About GF's legality filters?
Well...it's well known these filters are really poor. I've read about Pokémon whose current level was lower than their met level getting through PokéBank.

[Cecillia]

Yeah, I figured it was poor when terribly hackmons apparently went through and legals didn't

 

Edit: fixed the mons by using rng reporter, now two event mons are still not recognized.

Edited November 6, 2017 by Cecillia

[Ruby Genseki]

On 6/11/2017 at 12:39 PM, Cecillia said:

Edit: fixed the mons by using rng reporter, now two event mons are still not recognized.

Sorry, didn't see your edit at the time. Are you still having troule with these ones?
If so, could you upload them?

[Cecillia]

2 minutes ago, Ruby Genseki said:

Sorry, didn't see your edit at the time. Are you still having troule with these ones?
If so, could you upload them?

 

I fixed them. It were both Meloetta and Magmar. Magmar was correct thanks to you. Meloetta got corrected soon after

Edited November 14, 2017 by Cecillia