View source for Cable Club escape glitch

The '''Cable Club black out glitch''' is a glitch in {{2v2|Red|Blue}}. It was first documented by the user Paco81 on the Spanish Pokémon-Stats forum. Although fainting due to {{status|poison}} in the [[Cable Club]] is not possible as of {{game|Yellow}}, the glitch is possible in Pokémon Yellow via an expanded method requiring the [[Glitch City]] glitch.

The Cable Club black out glitch tricks the game into thinking that the player is still linked with another player when outside of the Cable Club and allows the player to encounter a copy of the other player's roster controlled by the AI of a chosen trainer class. The copy replaces any ordinary Trainer; for example, the glitch can be used on a [[Gym Leader]] to replace their roster with weaker Pokémon.

==Requirements==
In order to perform this glitch, the player must have met the following requirements;

*A poisoned Pokémon to faint in the Cable Club (Poison method)
*Access to the [[Safari Zone]] (Safari Zone method)
*A Pokémon with {{m|Dig}} (both Red/Blue and Yellow) (Safari Zone method)
*Access to the Cable Club, via another player with a copy of Red, Blue or Yellow and a [[Link cable]]

==Performing the glitch==
===Poison method===
The following method works only on Pokémon Red and Blue. First, the player needs to {{status|poison}} their Pokémon and be linked with another person. Preferably, the player then enters the trade center and initiates a trade with the other person or {{pkmn|battle}} with the other player to copy the roster into the game's memory for later use in the glitch. The player then presses cancel, or ends the battle and walks around until the poison causes the Pokémon to faint. After the Pokémon faints, the player will [[black out]] as normal, though the game still assumes the player to be linked.

===Safari Zone method===
The following method, generalized as the Cable Club escape glitch is an extended version of the glitch, which is also exploitable on Pokémon Yellow; however, due to the inability to Fly away from the Safari Zone in [[Generation I]], Dig must be used to escape the Safari Zone in Pokémon Yellow. The player must perform the first steps of the Glitch City glitch up to the point where they are bound to end up back in the Safari Zone gatehouse outside of the Safari Zone itself. The player must then enter the Cable Club, and walk around until their Safari Zone steps run out and they are returned to the [[gate]], activating the glitch.

To prevent a Trade Center or Colosseum Glitch City, the player can reenter the Safari Zone and Dig away. In Pokémon Red and Blue, poison can also be used to escape a Trade Center or Colosseum Glitch City, although this is redundant over the poison method.

==Effects==
After exploiting the glitch, the player is unable to [[saving|save]] under normal circumstances because the save button is replaced by the reset button. The player is also unable to open the [[Bag|item pack]], because normally items cannot be used when in link with another player. Provided that these settings are kept, if the player proceeds to encounter any Trainer outside of the Cable Club their roster will be replaced with the one last stored by the game when trading or battling with the player, and their picture will be replaced with {{ga|Red}}'s. Since the game is no longer receiving data from the other player, the name of the player simply becomes a blank space. The behavior of the other player is automatically controlled by the game and depends on the Trainer class; for example, encountering [[Bruno]] will make a Trainer appear with the other player's Pokémon, but a tendency to use {{DL|Battle item|X Defend}}. If the player did not trade or battle with the player, then a [[glitch Trainer]] with a glitchy name will appear instead with a team of [[glitch Pokémon]]; however, it is still technically the same Trainer class of the original Trainer, despite it having Red's picture. This is because a RAM address in the data structure is left checked to make all Trainer's have Red's picture and use the other player's Pokémon.

Unlike the 'death Trainer' found after the [[ZZAZZ glitch]], a Trainer with Red's picture cannot be found by encountering a wild Pokémon and will only be found when trying to encounter an existing Trainer. Remaining {{stat|HP}}, moves and status effects are also taken into account, meaning the other player could for instance replace Bruno's team with a poisoned level 5 {{p|Magikarp}} with 1 HP. If all of the player's Pokémon were fainted, a [[Charizard 'M]] or [[Q]] will be sent out instead.

Exclusively to Pokémon Yellow, the glitch also restricts poison in the overworld, because the poison method exclusive to Pokémon Red and Blue was fixed by restricting Pokémon outside of battle from losing HP due to poison when linked.

To restore the settings back to normal and be able to save, the player can simply reset the game, though any changes since entering the Cable Club are not saved. To be able to save the game, the player can simply change boxes. Alternatively, the player can enter the Cable Club again to be taken out due to inactivity, which restores the save button and allows the player to open the item pack again. Another method of restoring the options is to view the summary screen of any Pokémon in battle; this will allow the player to use their items again.

This glitch is useful for [[item duplication glitch|mass duplication of items]], as although changes to the item pack in the Cable Club are prohibited, items will be changed outside of the Cable Club even with the reset button. For example, a player could use a party of six [[Missingno.]], view the summary of a Pokémon in battle to restore the item pack to have one of their items duplicated, and then continuously swap the sixth item to duplicate many items in one battle. This glitch is also useful for encountering item mutating glitch Pokémon which are otherwise difficult or otherwise impossible to see on the opponent's side outside of the Cable Club.

==Video==
{{youtubevid|JgVUZPTt21E|ChickasaurusGL|Poison}}

{{Glitches}}<br>
{{Project GlitchDex notice}}