Anonymous user
Unnerve desync glitch: Difference between revisions
→YouTube video
No edit summary |
|||
(3 intermediate revisions by the same user not shown) | |||
Line 1:
{{Verify}}
The '''Unnerve
==Performing the glitch==
In order for this glitch to occur, battle animations must be enabled. One trainer should have a Pokémon with a held Berry (and possibly also the Cheek Pouch ability), which
* The Pokémon can have Cheek Pouch and be holding a Berry that doesn't restore HP, but rather attends to a nagging condition (such as Cheri Berry while it's paralyzed, or Leppa Berry while it has a move that's out of PP). In this case, the Pokémon needs to have '''more than 2/3 of its maximum HP remaining, but less than full HP.'''
* If the Pokemon is low enough in level, Oran Berry alone can be enough to trigger the glitch. In this case, the Pokémon needs to '''have 1/2 of its maximum HP remaining or less, but be within 9 HP of maximum''' (which together imply that its maximum HP can be no greater than 18). If the Pokémon has Ripen (doubling the Oran Berry's effect to 20 HP), the maximum HP threshold increases to 38, or if it has Cheek Pouch (which gains more HP after using the Berry), the maximum HP can be as high as 54.
* The Pokémon can have both Cheek Pouch and Sitrus Berry, in which case it needs to be in a narrow window where it has '''more than 5/12 of its maximum HP remaining, but no more than 1/2.''' In Generation VII only, the Berries that can potentially cause confusion (such as Figy Berry) can also be used, which slides the window down to '''more than 1/6 of its maximum HP, but no more than 1/4.'''
Next, one of two options needs to happen: either the Unnerve Pokémon uses Self-Destruct, Explosion, Misty Explosion, Final Gambit, Mind Blown, or Steel Beam to knock itself out and deal enough damage to knock out the Berry-wielding Pokemon as well (the simplest way to do this is by having a Mewtwo from the Virtual Console Generation I games learn Self-Destruct from TM36 there, then send it to Pokémon Bank where it will receive Unnerve as its ability), or else (only in a Double or Triple Battle), one of the Unnerve Pokémon's teammates can use a multi-target move to hit its teammate (which is processed first), then the Berry Pokémon, dealing enough damage to knock out both of them.
If battle animations are off, the visual representation of events in this case will show the Unnerve Pokémon faint before the
On the contrary, if battle animations are on, the visual sequence will show the
At this point, the behavior with animations off is a more accurate representation of the game state: the
==Effects==
If the undead Pokémon was one of the player's own, and the battle is not of a type that causes each team to be fully healed at the end, then ending the battle will cause it to be properly recognized as fainted, with 0 HP. Until that happens, though, the Pokémon menu will still show it as non-fainted, with the previously noted HP total, and the red and white dots showing each player's count of remaining healthy Pokémon will still count it as a healthy Pokémon.▼
▲If the undead Pokémon was one of the player's own, and the battle is not of a type that causes each team to be fully healed at the end, then ending the battle will cause it to be properly recognized as fainted, with 0 HP. Until that happens, though, the Pokémon menu will still show it as non-fainted, with the previously noted HP total, and (no matter whose side the undead Pokémon was on) the red and white dots showing each player's count of remaining healthy Pokémon will still count it as a healthy Pokémon.
Since a Pokémon just fainted, the player will be sent to a menu and forced to choose a replacement. The player can attempt to send out the undead Pokémon, but rather than failing with the usual message "There's no will to battle!" that accompanies a fainted Pokémon, the failure message will be "[Nickname] is already in battle!" Whichever Pokémon does get sent out next, the glitch will still persist afterward.
The player can use a Revive on the undead Pokémon, which will raise its visual HP to 1/2 of maximum plus the amount that it was shown fainting with. The Pokémon can then be sent back out to take more damage, and if it falls back to its desynchronized HP total, it will become undead again, with the same effects. Using a Max Revive instead will restore the fainted Pokémon to full HP by all accounts, and will end the effect of the glitch on it. Attempting to use any other healing item while it's still undead will fail, much like using a Full Heal on a Pokémon with no status condition, and the player's turn will be wasted with no effect.
If a trainer's team is reduced to only the undead Pokémon plus other Pokémon that are truly fainted in all regards, the game will correctly recognize at that point that their entire team has been defeated, and that trainer will lose the battle and/or black out, after which time the effects of the glitch will end and their Pokémon will be healed.
Other than the initial menu to replace the undead Pokémon, the trainer whose team it's on will have the option to switch to it on a later turn while it's still undead, and this switch, if the trainer chooses to make it, will not fail. In a Single Battle, if it's ever sent out again, the game is effectively stuck: the player will still receive an action menu at the beginning of each turn, but any actions they select from that menu will be skipped, including selecting moves, switching Pokémon, using items from the Bag in battles that allow it, running away or forfeiting, or attempting to call upon Mega Evolution or Dynamax. The opponent will still be able to use moves, but any move that targets the undead Pokémon will be treated as though there's not actually a Pokémon there, and will fail as a result. Notably, this includes Struggle, so the opponent will not be able to hit with Struggle and will not damage itself with recoil,
==Twitter video==
{{Twitter|zakocky/status/1440226387747475460|Zaggyo}}
==YouTube video==
{{YouTube|
[[Category:Generation VI glitches]] [[Category:Generation VII glitches]] [[Category:Generation VIII glitches]]
|