Jump to content

CFC4 freeze: Difference between revisions

Fixed grammar and wording to accurately reflect how this freeze happens.
(added details for why this glitch occurs.)
(Fixed grammar and wording to accurately reflect how this freeze happens.)
 
Line 3:
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, storesknown as wFontLoaded, acts as a check to see if athe font is loaded, and is thus known as wFontLoaded. If the firstleast-significant bit of this address is set, thus beingdenoting an odd value, then whenwhenever the game needs to load a new tileset into VRAM, the game copies tileset data during VBlank. If the valueaddress iscontains an even value, then data is instead copied while the LCD is disabled. BecauseIf this valueaddress is setcorrupted to 1an odd value during battle, then when exiting the battle, the game goes through a code path that resultscauses init waitingto wait for a VBlank interrupt that will never arrive, due to the LCD being turned off during the battle transition from battle to overworld.
 
The freeze can be avoided by performing a glitch that would normally cause it to occur in Diglett's Cave.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.