Glitch City RAM manipulation (buffer overflow techniques): Difference between revisions
Jump to navigation
Jump to search
Glitch City RAM manipulation (buffer overflow techniques) (view source)
Revision as of 23:01, 13 June 2023
, 1 year agono edit summary
mNo edit summary |
mNo edit summary |
||
Line 5:
Though Glitch City RAM manipulation has its benefits, there may still be some limitations.
*For corruptions where a [[0x50 sub-tile]] (interpreted as the 0x50 end control character) is needed to end a corruption, it means there cannot be corruptions where 0x50 is in the middle but where data past the 0x50 is required for the corruption. (many such as the above oobLG, as well as simpler buffer overflow techniques such as [[Move 0x00 corruption (Generation I)|CoolTrainer♀]] or [[LOL glitch]] (based on [[unterminated name glitch item]] abuse)).
*When using the contents of the screen to print text. For example, the [[Rival LOL glitch]] requires the 0x53 sub-tile which prints the Rival's name (from RAM D34A-D351 (-1 in Yellow)) on the screen to be saved later with a screen saving glitch item. However, control characters in the Rival's name (such as control characters more than one tile long, line break characters, text from another RAM address) will interfere with the required sub-tile.
**Similarly, this applies for any unterminated name glitch items which print tiles depending on the contents of the screen (tile-writing glitch items).
| |||