CFC4 freeze: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>Torchickens No edit summary |
>Torchickens No edit summary |
||
| Line 7: | Line 7: | ||
The following [[glitch]]es are known for corrupting CFC4. |
The following [[glitch]]es are known for corrupting CFC4. |
||
*"Bad CoolTrainers" (see [[- (move)]]) |
*"Bad CoolTrainers" (see [[- (move)]]). Internal coordinates (can be viewed on BGB) for the tile that determines CFC4 in English versions is at Y=5 X=1. |
||
*[[Wild appeared!]] (with 220+ or 0 Pokémon) |
*[[Wild appeared!]] (with 220+ or 0 Pokémon) |
||
*Other [[buffer overflow]] techniques such as [[Super Glitch (Generation I)|Super Glitch]] |
*Other [[buffer overflow]] techniques such as [[Super Glitch (Generation I)|Super Glitch]] |
||
Revision as of 12:39, 30 September 2019
| This article is incomplete. Please feel free to add any missing information about the subject. It is missing: Why this occurs and why Diglett's Cave works as a solution. |
The CFC4 freeze occurs in Pokémon Red and Blue. It does not occur in Pokémon Yellow. If the value of memory address CFC4 is an odd value, it can cause the game to freeze after the conclusion of a battle.
The freeze curiously, can be avoided by performing a glitch that would normally cause it to occur in Diglett's Cave.
The following glitches are known for corrupting CFC4.
- "Bad CoolTrainers" (see - (move)). Internal coordinates (can be viewed on BGB) for the tile that determines CFC4 in English versions is at Y=5 X=1.
- Wild appeared! (with 220+ or 0 Pokémon)
- Other buffer overflow techniques such as Super Glitch
- During instant encounter infinite chain glitch
This article or section is a stub. You can help Glitch City Wiki by expanding it. 
|