CFC4 freeze: Difference between revisions
added details for why this glitch occurs.
>Torchickens No edit summary |
CytricAcid (talk | contribs) (added details for why this glitch occurs.) |
||
Line 1:
{{incomplete|Why
The '''CFC4 freeze''' occurs in {{RB}}. It does not occur in {{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.
Specifically, the value CFC4 stores a check to see if a font is loaded, and is thus known as wFontLoaded. If the first bit is set, thus being an odd value, then when the game needs to load a new tileset into VRAM, the game copies tileset data during VBlank. If the value is an even value, then data is copied while the LCD is disabled. Because this value is set to 1 during battle, the game goes through a code path that results in waiting for VBlank interrupt that will never arrive, due to the LCD being turned off during the battle transition to overworld.
The freeze curiously, can be avoided by performing a glitch that would normally cause it to occur in Diglett's Cave.▼
▲The freeze
The following [[glitch]]es are known for corrupting CFC4.
Line 11 ⟶ 13:
*Other [[buffer overflow]] techniques such as [[Super Glitch (Generation I)|Super Glitch]]
*During [[instant encounter infinite chain glitch]]
==Source==
[https://youtu.be/vJfjYeFlj-g?t=376 ZZAZZGlitch's video on Overanalysing Glitch Items(paraphrased)]
{{stub}}
| |||