Most of the opposition to implementing this glitch into our simulator is really a question of whether we should take developer intent into account when we decide how to simulate the game. If we assume that yes, developer intent is important, then we should remove the following glitches from the game:
Currently, if a Pokemon with Flash Fire is frozen, when it is hit by a Fire attack it is thawed and takes damage, rather than being thawed and activating Flash Fire. This is clearly not what was intended. The glitch probably results from Game Freak wanting Fire moves to thaw Flash Fire Pokemon, but not being careful about where they put each check in the queue.
When a Pokemon is frozen, the Fire move cannot 'power up' the Pokemon's fire power because its fire power is disabled. When a Pokemon is frozen, it is susceptible to Fire. How does this not make sense?
You cannot use Chatter on a non-Chatot Pokemon. It cannot be Sketched, Assisted, Mimicked, etc.. This is because it requires a call to Chatot's cry to determine the confusion rate. Surely Game Freak didn't want this to happen.
This isn't likely a glitch, Chatot is a unique Pokemon and the move is probably not meant to be Sketched. It requires the ability to change its cry and learn phrases, which Smeargle cannot do. I do not doubt that this was intentional.
It's only through a flaw in the random number generator that certain IV combinations are impossible on non-breedable Pokemon. This was most certainly not intended by Game Freak, and thus should be fixed on our simulator.
This isn't a glitch, Nintendo uses many IV generation methods for different methods of obtaining Pokemon. It's also an effective guard against hacked Pokemon.
If a Pokemon with a Choice item uses Sleep Talk, Sleep Talk must be chosen but will always fail. Surely the intended effect is that you must choose the move that was selected by Sleep Talk.
It fails because it requires the Pokemon to use in effect two moves. First, Sleep Talk, and then the move it selects. Using two moves is in violation of the limitation placed on Pokemon holding a Choice item.
We should fix Dream Eater so it works on Substitutes. All of the other draining moves do.
The attack hits the Substitute, and the Substitute is not asleep, the Pokemon is.
Life Orb's 10% recoil does not activate when the attack is used on a Substitute. This should be fixed as well.
Life Orb only yields 10% recoil damage when it succeeds in damaging the foe, and Substitute prevents that from happening.
OHKOs don't actually OHKO Pokemon, they do damage equal to their max HP. If you pass a Substitute with more HP than the target's max HP, OHKOs will actually fail to break the Substitute. The obvious mechanic would be that OHKOs OHKO stuff, so they should always break the Substitute.
OHKOs, like all attacks, are targeted toward the foe. But the Substitute is a decoy. When a decoy from another Pokemon has more durability than the foe itself, the OHKO which was intended to OHKO the foe will fail to do the necessary damage to break the foe's 'borrowed' Substitute. If it was the foe's own Substitute, then of course it would break the Substitute, because the foe's own Substitute would simply be 1/4 as durable as the foe.
Substitute should block the effects of Static, Poison Point, etc. It makes no sense at all (and obviously goes against the status-blocking wishes of Game Freak for Substitute) that Substitute doesn't block being put to sleep by Effect Spore.
Not at all, Substitute again is a decoy that takes damage from the opponent, including taking Status attacks. Substitutes cannot be statused. However, when the Pokemon attacks from behind the Substitute, the Pokemon does the attacking, not the Substitute. If the Pokemon behind the Substitute makes contact with the foe, it makes itself susceptible to the foe's ability. This is shown even in the animation in the game, when the Pokemon pops out from behind its Substitute to do the attacking, then immediately goes behind it again.
Reflect / Light Screen should not be broken when Brick Break hits a Ghost. Ghosts block Rapid Spin, so why should they not block this? Must be an oversight by Game Freak; I'm sure they'll fix it in the English release of Platinum, as long as they're aware of it.
Agreed. Brick Break acts as it is supposed to, the Rapid Spin issue is the glitch. FUCK RAPID SPIN. FIX IT, bitches!!!!!!
