Jump to content

Party scrolling memory corruption: Difference between revisions

(Created page with "'''Party scrolling memory corruption''' is a glitch in {{RGBY}} documented by TheZZAZZGlitch (and Evie for the HRAM modification method). Note it may function differently in t...")
 
Line 275:
==HRAM manipulation==
{{Researchneeded|1=More technical specifics}}
Altering the glitch by altering FF81 in HRAM (currently, the only ways known to do this are with [[arbitrary code execution]] and possibly [[connection copier]]) will corrupt the memory in a different way relative to the new upper address in the memory (which was previously C3). If for instance, the OAM DMA buffer starts at C4XX, the first Pokémon may touch C3B4, the second C3DC, the third C404, the fourth C42C, the fifth C454 and the sixth C47C; which allows altering memory addresses later before, hence from this relationship of +0x28 for the next Pokémon, C3B4+(0x28*[n-1])=the address to corrupt where n is the desired Pokémon slot, or (address/0x28)}-(C3B3/0x28) is used to locate the cursor position the player was on (or needs to be on) before the corruption.
 
Details however are relative to the upper address chosen, and this same logic might not work for ones different to C4XX.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.