Partial trapping move Mirror Move link battle glitch: Difference between revisions

Jump to navigation Jump to search
Content added Content deleted
VisualWikitext
>Torchickens
No edit summary
>Torchickens
No edit summary
Line 1: Line 1:
{{Misc R/B}}
{{Misc R/B}}
{{credit|Reported by=SloshedMail|Verified by=Torchickens}}
{{credit|Reported by=SloshedMail|Verified by=Torchickens}}
[[File:Fire Spin glitch fainted Pokémon.png|frame|right|Player two having apparently sent out a Spearow that just fainted after the Fire Spin glitch was caused.]]
The '''Fire Spin glitch''' is a Link Battle de-sync glitch in Pokémon Red, Blue and Yellow.


The '''Fire Spin glitch''' is a miscellaneous glitch which is only known to exist within the [[bp:Generation I|first generation]] of the Pokémon games. By definition, it is a glitch which activates an oversight in the two-player capabilities of the game's battling system. On one user's side, one of his or her Pokémon has not fainted, but on the other user's side the same Pokémon has fainted, meaning that [[transmission error]]s will persist until the battle ends.
It is a glitch which activates an oversight in the two-player capabilities of the game's battling system. On one user's side, one of his or her Pokémon has not fainted, but on the other user's side the same Pokémon has fainted, meaning that [[communication error]]s will persist until the battle ends.


==Requirements==
==Requirements==
Line 9: Line 11:
#Access to the Cable Club.
#Access to the Cable Club.
#A working link cable.
#A working link cable.
#Player One requires a Pokémon knowing [[bp:Mirror Move|Mirror Move]].
#Player one requires a Pokémon knowing [[bp:Mirror Move|Mirror Move]].
#Player Two requires a Pokémon knowing [[bp:Fire Spin|Fire Spin]].
#Player two requires a Pokémon knowing [[bp:Fire Spin|Fire Spin]].
#On Player One's side; a Pokémon which could be defeated in one move by Fire Spin.
#On player one's side; a Pokémon which could be defeated in one move by Fire Spin.
#Ideally Player One should have the Pokémon knowing Mirror Move as the first party member.
#Ideally player one should have the Pokémon knowing Mirror Move as the first party member.
#Ideally Player Two should have the Pokémon knowing Fire Spin as the first party member.
#Ideally player two should have the Pokémon knowing Fire Spin as the first party member.


==Method==
==Method==


#Both players should enter the Cable Club and request a battle.
#Both players should enter the Colosseum via the Pokémon Cable Club and battle.
#In battle, Player One should send out the Pokémon knowing Mirror Move and Player Two should send out the Pokémon knowing Fire Spin.
#In battle, player one should send out the Pokémon knowing Mirror Move and player two should send out the Pokémon knowing Fire Spin.
#If the Pokémon knowing Mirror Move is faster, have the opponent use Fire Spin and wait until the Pokémon escapes it. If the Pokémon knowing Mirror Move is slower, have the opponent use Fire Spin and hope it misses, then on the same turn Mirror Move it.
#Player Two should perform the move Fire Spin first, whilst Player One should use Mirror Move.
#Player two should switch his/her Pokémon to one that can be defeated in one hit by Fire Spin, and have it hit. If it doesn't hit, you'll have to try the glitch again to see its other effects.
#Due to Mirror Move's priority; the turn should end before the move is used.
#Player Two should switch his/her Pokémon to one that can be defeated in one hit by Fire Spin.
#If performed correctly, on player two's screen Mirror Move will fail and his/her Pokémon would not faint. On player one's screen however, the game considers that player two's Pokémon has fainted if Fire Spin hit.
#Communication errors will persist, including the opposing players sending out a Charizard 'M or Q, the fainted Pokémon or another glitchy Pokémon.
#If performed correctly, on Player Two's screen Mirror Move will fail and his/her Pokémon would not faint. On Player One's screen however, the game considers that Player Two's Pokémon has fainted.
#The game will then translate data from other parts of the RAM to manage what will happen next in battle, for example; what Pokémon Player One switches to. The [[TMTRAINER effect]] is common here.


<table align="center" style="border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -khtml-border-radius: 10px; -icab-border-radius: 10px; -o-border-radius: 10px; border: 2px solid #828282; background: #cccccc;">
<table align="center" style="border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -khtml-border-radius: 10px; -icab-border-radius: 10px; -o-border-radius: 10px; border: 2px solid #828282; background: #cccccc;">
<tr>
<tr>
<td width="425px" colspan="2" style="line-height:10px"><center>[b][http://www.youtube.com/watch?v=O8GMyy7x3WE There is now a video regarding the glitch. By SloshedMail][/b]</center>
<td width="425px" colspan="2" style="line-height:10px"><center>[b][http://www.youtube.com/watch?v=O8GMyy7x3WE Youtube video by SloshedMail][/b]</center>
</td></tr></table><br clear="all" />
</td></tr></table><br clear="all" />


Retrieved from "https://glitchcity.wiki/wiki/Partial_trapping_move_Mirror_Move_link_battle_glitch"