I’m not sure if its a bug or its a buff to the ability. But man I never saw that before!
I was just grinding some exp before giovanni. since when the heck is that a thing?
by danjanah
7 Comments
[deleted]
[deleted]
Bewear_Star_9
Oh yeah that a bug in gen 3 that wasn’t full understood until 2018
rain4kamikaze
It’s an old bug from like 15 years ago i think, understood better about a few years ago. I think I remember it as something like this:
In gen 3, multi hit moves that make contact with abilities that does status effects, has a weird glitch that can inherit the current status you have and apply it at the end (after the multi hit move finishes).
Eg in your case:
Spearow uses Fury Attack. Fury attack first few hits and causes Static to trigger, paralyzing Spearrow. Fury attack continues but does not trigger static (you can’t see that anymore because you’re paralyzed anyways) but the calculations continue in the background. The glitch occurs because contact abilities has a variable that stores the status (eg. para, burn etc) and clears that variable off once the moves end, but multi hit moves don’t end immediately. At the end of the multihit move, there is a check for status effect move (which is now para, because of that variable from static), but the multihit move has 0 effect chance. The glitch here is also that there is a less than or equal to 0 effect chance trigger in the calculation. So the move tries to apply paralysis with a nonzero number, i think it’s 1/255 chance.
This shows up as the pokemon’s abilty causing paralyze.
The long story is that, with multihit moves like Twinneedle being introduced, the final hit itself checks for status effect (because 20% chance for poison). The other multihit move don’t have status effects, but they’re coded similarly to twineedle.
Usually it will try to roll for status effect with 0 effect chance for [no status effect], which does nothing. but now it tries to roll for status effect with 0 effect chance for [paralyze] which is the variable inherited by static. And because of this bug in this gen3 game, the game will trigger the secondary effect status effect if the RNG value is less than **or equal** to 0, which is like 1/255 chance. There’s 2 bugs at play here.
Inherited a piece of history straight from gen3, in the switch 2.
7 Comments
[deleted]
Oh yeah that a bug in gen 3 that wasn’t full understood until 2018
It’s an old bug from like 15 years ago i think, understood better about a few years ago. I think I remember it as something like this:
In gen 3, multi hit moves that make contact with abilities that does status effects, has a weird glitch that can inherit the current status you have and apply it at the end (after the multi hit move finishes).
Eg in your case:
Spearow uses Fury Attack. Fury attack first few hits and causes Static to trigger, paralyzing Spearrow. Fury attack continues but does not trigger static (you can’t see that anymore because you’re paralyzed anyways) but the calculations continue in the background. The glitch occurs because contact abilities has a variable that stores the status (eg. para, burn etc) and clears that variable off once the moves end, but multi hit moves don’t end immediately. At the end of the multihit move, there is a check for status effect move (which is now para, because of that variable from static), but the multihit move has 0 effect chance. The glitch here is also that there is a less than or equal to 0 effect chance trigger in the calculation. So the move tries to apply paralysis with a nonzero number, i think it’s 1/255 chance.
This shows up as the pokemon’s abilty causing paralyze.
The long story is that, with multihit moves like Twinneedle being introduced, the final hit itself checks for status effect (because 20% chance for poison). The other multihit move don’t have status effects, but they’re coded similarly to twineedle.
Usually it will try to roll for status effect with 0 effect chance for [no status effect], which does nothing. but now it tries to roll for status effect with 0 effect chance for [paralyze] which is the variable inherited by static. And because of this bug in this gen3 game, the game will trigger the secondary effect status effect if the RNG value is less than **or equal** to 0, which is like 1/255 chance. There’s 2 bugs at play here.
Inherited a piece of history straight from gen3, in the switch 2.
[Yes, it’s a bug](https://bulbapedia.bulbagarden.net/wiki/List_of_battle_glitches_in_Generation_III#Multistrike_moves_inflict_status_upon_their_target)
There have been several posts about it since the release of FR/LG on Switch.
Known bug
Just wanted to say as a Dragon Age fan, I love the name you gave your Electrode, it’s hilarious.
How the hell…
Somehow I didn’t know this was a thing. This franchise is truly full of surprises.