Party scrolling memory corruption: Difference between revisions

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 than before (as the old C3 value cannot be used to corrupt beyond D2FX+), 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. Echo RAM may come into place, for example; the EB64 from slot 255 should touch CB64 on an accurate platform.