59,093
edits
Thunder Jolt: Difference between revisions
m
Text replacement - " ==" to " =="
m (→Origin: grammar) |
m (Text replacement - " ==" to " ==") |
||
| Line 20: | Line 20: | ||
===Staleness glitch=== | ===Staleness glitch=== | ||
Thunder Jolt has a glitch relating to [[stale-move negation]] that began in ''Melee'' and has appeared in every game since. When the move is used in the air and then lands, the arcing wave created points its staleness slot to whatever the user is doing, rather than to match the staleness slot of the object that created it (the aerial ball). This means that if the user is doing another move when the projectile lands, the arcing wave's staleness will act as if it were that move when it connects. For example, if Pikachu is doing an up smash, the wave will use the current staleness of Pikachu's up smash, and if it hits it will stale the up smash. If the user is not doing an attack (e.g. simply standing), the projectile will not have any stale slot, dealing base damage (neither fresh nor stale) and not advancing the queue at all. | Thunder Jolt has a glitch relating to [[stale-move negation]] that began in ''Melee'' and has appeared in every game since. When the move is used in the air and then lands, the arcing wave created points its staleness slot to whatever the user is doing, rather than to match the staleness slot of the object that created it (the aerial ball). This means that if the user is doing another move when the projectile lands, the arcing wave's staleness will act as if it were that move when it connects. For example, if Pikachu is doing an up smash, the wave will use the current staleness of Pikachu's up smash, and if it hits it will stale the up smash. If the user is not doing an attack (e.g. simply standing), the projectile will not have any stale slot, dealing base damage (neither fresh nor stale) and not advancing the queue at all. | ||
==Instructional quotes== | ==Instructional quotes== | ||