-
-
Notifications
You must be signed in to change notification settings - Fork 672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gen 3 Breeding PID Legality #3092
Comments
Not a bug. Please do not report invalid encounters being flagged as invalid; they are flagged as invalid for a reason. Hold control to see that your PIDIV is incompatible with the encounter it was matched to, hence the Encounter Type PID mismatch. |
I don't understand. |
Yeah, and it's not statistically probable to get a 1:billion match, hence the flag. |
But these eggs must be considered as legal. |
No they cannot be obtained without an external tool or unnecessary manipulation -- you are unable to change parents once the egg is ready for pickup (PID set). Again, the statistical improbability of randomly getting a PIDIV correlation is exponentially lower than the chance that someone hacks something with a PIDIV incorrectly. |
The first shiny Horsea has been obtained with only rng manipulations. |
Just because you can doesn't mean you should. |
Recently I rng'd a Kingdra from the Battle Pyramid and I caught it in a Poké Ball using the Pomeg Glitch.
When I read my Emerald save file with PKHeX, the Kingdra is considered as illegal and that makes sense.
But when I transfer it into Gen 4 he's still considered as illegal cause of "PID mismatch".
So I checked if the PID and IVs of my Kindgra were possible via breeding in Emerald and yes it can.
Emerald Breeding RNG Process : https://github.com/Admiral-Fish/PokeFinder/blob/master/Core/Gen3/Generators/EggGenerator3.cpp#L131
To support my words I was able to rng'd a Horsea egg with the same pid/ivs that the Kingdra using lua script + battle video.
![Screenshot_1](https://user-images.githubusercontent.com/65578604/99859610-d001dc80-2b90-11eb-9ad9-494015196efb.png)
![Screenshot_4](https://user-images.githubusercontent.com/65578604/99859613-d1cba000-2b90-11eb-92ad-ec42509fa07b.png)
And PKHeX considered it as illegal. I use the last PKHeX version.
![Screenshot_2](https://user-images.githubusercontent.com/65578604/99859660-f6277c80-2b90-11eb-8c7b-73c9b725484d.png)
The text was updated successfully, but these errors were encountered: