- (glitch Pokémon): Difference between revisions

- (glitch Pokémon) (view source)

Revision as of 01:34, 27 March 2014

97 bytes removed , 27 March 2014

m

→‎The forced switch Pomeg sub-glitch: When the game is running but cannot be played, it's called a lockup

Leafbarrett

26

edits

Revision as of 15:50, 20 February 2014 (view source) Tiddlywinks (talk \| contribs) m (→‎The forced switch Pomeg sub-glitch: non-redirected link) ← Older edit		Revision as of 01:34, 27 March 2014 (view source) Leafbarrett (talk \| contribs) m (→‎The forced switch Pomeg sub-glitch: When the game is running but cannot be played, it's called a lockup) Newer edit →
Line 23:		Line 23:
	óË {e Ái, will occur when a Pokémon with "negative" (i.e. 65535 or below) health (from the [[Pomeg glitch]]) is traded from Pokémon Emerald to Pokémon FireRed or LeafGreen versions and a healing item is used, resetting the Pokémon's HP to 0 when there are no other Pokémon available for battle. The player will not [[black out\|white out]] because healing can never activate the 'no Pokémon left' flag. The 'no Pokémon left' flag only activates when the player's last Pokémon faints due to damage of some kind.		óË {e Ái, will occur when a Pokémon with "negative" (i.e. 65535 or below) health (from the [[Pomeg glitch]]) is traded from Pokémon Emerald to Pokémon FireRed or LeafGreen versions and a healing item is used, resetting the Pokémon's HP to 0 when there are no other Pokémon available for battle. The player will not [[black out\|white out]] because healing can never activate the 'no Pokémon left' flag. The 'no Pokémon left' flag only activates when the player's last Pokémon faints due to damage of some kind.

	By using the method above, entering a battle with all fainted Pokémon and using a [[Revive]] on another fainted Pokémon will immediately take the player to the Pokémon selection menu. However, for unknown reasons selecting the revived Pokémon will prompt the player that the opponent "is about to switch Pokémon". Returning to the Pokémon selection menu via the "YES" option but choosing Cancel instead of choosing the revived Pokémon will force the player to send out óË {e Ái. It is impossible to use because when it is sent out in battle, the game will ~~loop~~ its entry animation without end~~. It shouldn't be considered a "freeze" as the game still runs. This simply causes no further action to occur~~.		By using the method above, entering a battle with all fainted Pokémon and using a [[Revive]] on another fainted Pokémon will immediately take the player to the Pokémon selection menu. However, for unknown reasons selecting the revived Pokémon will prompt the player that the opponent "is about to switch Pokémon". Returning to the Pokémon selection menu via the "YES" option but choosing Cancel instead of choosing the revived Pokémon will force the player to send out óË {e Ái. It is impossible to use because when it is sent out in battle, the game will lock up, looping its entry animation without end.