Not A Bug Types have undefined behavior in generations where they don't exist

Sabby60

Sabby60

What type of bug are you reporting? Chat

What is the bug?
/coverage and /nds: types that don't exist in the given generation are missing certain type matchups
Details:
- maxgen1: Dark isn't super effective against anything; Steel isn't resisted by Fire; Fairy isn't resisted by anything
- maxgen2 and mod=moderngen2: Fairy isn't resisted by Fire
- maxgen3-5: Fairy isn't resisted by Steel
Any unmentioned type matchups function correctly.

Are you able to replicate it? If so, how?
Examples:

/coverage fairy,gen1:
Super Effective: Dragon, Fighting
Neutral: Bug, Fire, Ghost, Ice, Poison, Psychic, Electric, Grass, Flying, Ground, Normal, Rock, Water
Resists: None
Immunities: None

/nds maxgen4,resists fairy,multitype:
Arceus-Fire, Arceus-Poison
 
Why would this be a bug exactly? Dark and Fairy types don't exist in generation 1 for example, if you try to run coverage or weakness searches with these types your going to get undefined behavior. The only improvement I could see here would be banning non-existent types from these searches eg: no Dark type in gen 1.

As for why this happens and why things work normally in battle if you use custom game to bypass validation? PS is built current gen down, namely everything is added for the most recent gen it was defined in. Then each past generation is a mod that modifies the generation that comes after it. When you for example go from gen 6 to 5, fairy type still exists, its just blocked from use by the validator.
 
HoeenHero said:
Why would this be a bug exactly? Dark and Fairy types don't exist in generation 1 for example, if you try to run coverage or weakness searches with these types your going to get undefined behavior. The only improvement I could see here would be banning non-existent types from these searches eg: no Dark type in gen 1.

As for why this happens and why things work normally in battle if you use custom game to bypass validation? PS is built current gen down, namely everything is added for the most recent gen it was defined in. Then each past generation is a mod that modifies the generation that comes after it. When you for example go from gen 6 to 5, fairy type still exists, its just blocked from use by the validator.
Click to expand...
I reported this because I found it weird that some of the type matchups work and some of them don't. In hindsight, though, this bug is pretty insignificant (I only found it because I was doing research on Scavengers params, and I don't think it impacts anything else).
 
You must log in or register to reply here.
Back
Top