Jump to content

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

Partial trapping move Mirror Move link battle glitch (view source)

Revision as of 22:31, 31 May 2014

230 bytes added ,  10 years ago
no edit summary
VisualWikitext
>Torchickens
No edit summary
>Torchickens
No edit summary
Line 1:
{{Misc R/B}}
{{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, itIt 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 [[transmissioncommunication error]]s will persist until the battle ends.
 
==Requirements==
Line 9 ⟶ 11:
#Access to the Cable Club.
#A working link cable.
#Player Oneone requires a Pokémon knowing [[bp:Mirror Move|Mirror Move]].
#Player Twotwo requires a Pokémon knowing [[bp:Fire Spin|Fire Spin]].
#On Playerplayer Oneone's side; a Pokémon which could be defeated in one move by Fire Spin.
#Ideally Playerplayer Oneone should have the Pokémon knowing Mirror Move as the first party member.
#Ideally Playerplayer Twotwo should have the Pokémon knowing Fire Spin as the first party member.
 
==Method==
 
#Both players should enter the Colosseum via the Pokémon Cable Club and request a battle.
#In battle, Playerplayer Oneone should send out the Pokémon knowing Mirror Move and Playerplayer Twotwo 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.
#PlayerIf Twoperformed shouldcorrectly, switchon player two's screen Mirror Move will fail and his/her Pokémon towould not faint. On player one's thatscreen canhowever, bethe defeatedgame inconsiders onethat hitplayer bytwo'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;">
<tr>
<td width="425px" colspan="2" style="line-height:10px"><center>[b][http://www.youtube.com/watch?v=O8GMyy7x3WE There is now aYoutube video regarding the glitch. Byby SloshedMail][/b]</center>
</td></tr></table><br clear="all" />
 
Anonymous user
Retrieved from "https://glitchcity.wiki/wiki/Special:MobileDiff/30152"
Cookies help us deliver our services. By using our services, you agree to our use of cookies.
More information