Validator Kakuna/Beedrill in metagames with Gen 2 sources

DaWoblefet

DaWoblefet

Demonstrably so
is a Battle Simulator Administratoris a Community Leaderis a Top Programmeris a Community Contributoris a Top Researcheris a Top Tiering Contributoris a Social Media Contributor Alumnus
PS Admin
What type of bug are you reporting? Validator

What is the bug?
Kakuna and Beedrill should be able to learn Poison Sting, Harden, and String Shot simultaneously in Gen 2 and Gen 1 tradeback formats, but currently cannot. That combination should be illegal in Gen 1 only, because in those games, Kakuna did not have a learnsets entry for Harden at level 7 (unlike Metapod).

Are you able to replicate it? If so, how?
Kakuna
Ability: No Ability
- Harden
- Poison Sting
- String Shot

This should be legal in Gen 2 OU, legal in Gen 1 Tradebacks OU, illegal in Gen 1 OU. For the developer: there is a hardcode in the Gen 2 validator file for this exception, which Gen 1 is inheriting from. It's not as simple as just moving the hardcode from Gen 2 to Gen 1, because then it would not be legal in tradebacks.
 
Last edited:
I can take this. All of those hardcoded move incompatibilities are exclusive to gen 1 but incorrectly applied to gen2.
 
Is only Kakuna affected? The easy hack would be to change its '1L1' entry to '1Eany' which makes the Gen 1 OU team validator complain that "Kakuna's moves Harden, Poison Sting are incompatible." allowing the incompatibility to be removed from the ruleset.
 
urkerab said:
Is only Kakuna affected? The easy hack would be to change its '1L1' entry to '1Eany' which makes the Gen 1 OU team validator complain that "Kakuna's moves Harden, Poison Sting are incompatible." allowing the incompatibility to be removed from the ruleset.
Click to expand...

Would that cover the gen 1 tradebacks case?
 
Okay then, I can look into that and see if it can also work for the other illegal combinations

ETA: it doesn't work for the other combinations without breaking things. Plus the logic should frankly work without having to doctor the learnset data. I think the quickest fix here (which is still a bit of a hack, since ideally the validator would catch this from first principles) is to just move the ruleset data to the right generation(s).
 
Last edited:
You must log in or register to reply here.
Back
Top