Anonymous user
CFC4 freeze: Difference between revisions
Fixed grammar and wording to accurately reflect how this freeze happens.
>Torchickens No edit summary |
(Fixed grammar and wording to accurately reflect how this freeze happens.) |
||
(One intermediate revision by one other user not shown) | |||
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 stored at address CFC4, known as wFontLoaded, acts as a check to see if the font is loaded. If the least-significant bit of this address is set, denoting an odd value, then whenever the game needs to load a new tileset into VRAM, the game copies tileset data during VBlank. If the address contains an even value, then data is instead copied while the LCD is disabled. If this address is corrupted to an odd value during battle, then when exiting the battle, the game goes through a code path that causes it to wait for a VBlank interrupt that will never arrive, due to the LCD being turned off during the transition from battle 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}}
|