-
-
Notifications
You must be signed in to change notification settings - Fork 701
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 Egg PID\IV Combo Matching Wild\Static PID\IV #3894
Comments
This is intended. Preferred behavior is to flag a statistically improbable egg (where every person who reports this has to go out of their way to RNG manipulate it) since it is way more likely to be a bad hack. Refer to: #3092 (comment) If you RNG manipulated it, you know what you did and you can just ignore it. |
Oh I see:
Seems more fitting of the "Fishy" tag rather than straight up illegal, since as that thread describes it is technically possible. Calling this "Invalid" just isn't true. Seeing as you're familiar with RNG manipulation and consider it a valid\legal way of obtaining Pokemon. |
This is not going to be changed. This is the preferred behavior.
|
To begin with, every legal mon is statistically improbable. I would challenge the claim that it is more likely that: given a met level of zero and a method1/2/4 PID match, the more likely scenario is that someone knew "just enough" to fake every aspect of the mon except its met level being non-zero compared to someone RNG manipulating it. This reeks of https://en.wikipedia.org/wiki/Prosecutor%27s_fallacy |
1:(2^32) < {chance of someone making a bad hack} As @Lusamine already linked, this has been discussed before. |
Describe the problem
When a bred Pokemon in Gen 3 has a PID and IV combination that matches standard Method 1/2/4, it flags it as "Encounter Type PID Mismatch." However, its my understanding that Eggs generated in Emerald can have arbitrary PID and IV combinations and thus should be able to generate identical combinations to natural encounters.
To Reproduce
Use RNG Manipulation to lock in a specific PID, with Parents who have the correct IV inheritance to yield an offspring with IVs that match a valid Method 1/2/4 encounter exactly.
Expected behavior
PkHex already correctly identifies attached Gengar as coming from an Egg, but because it finds a matching Method 1 PID\IV spread, it flags as illegal. Admittedly an extreme edge case, and HIGHLY improbable from normal gameplay but technically possible.
Additional context
Invalid: Encounter Type PID mismatch.
Valid Move 1: E-Learned by Level-up. @ lv1
Valid Move 2: E-Learned by Level-up. @ lv1
Valid Move 3: E-Learned by Level-up. @ lv13
Valid Move 4: E-Learned by Level-up. @ lv16
Fishy : All EVs are zero, but leveled above Met Level. (Used Rare Candies)
Fishy : Current experience matches level threshold. (Used Rare Candies)
Valid : Able to hatch a traded Egg at Met Location.
Valid : Nickname matches species name.
Valid : All ribbons accounted for.
Valid : Ability matches ability number.
Valid : Correct ball for encounter type.
Valid : Gender matches PID.
Valid : Nature matches PID.
Encounter Type: Egg (Gastly)
Location: Littleroot Town
PID Type: Method_1
Origin Seed: 88E476FF
094 - GENGAR - 13A70A26ADC2.zip
The text was updated successfully, but these errors were encountered: