Anonymous user
Bad sprite: Difference between revisions
Jump to navigation
Jump to search
no edit summary
>Torchickens No edit summary |
No edit summary |
||
Line 4:
Most commonly in {{RBY}} the sprite will affect the SRAM and possibly [[Hall of Fame corruption|corrupt the Hall of Fame]].
A bad sprite that causes a [[glitch battle]] is typically due to bad sprite dimensions. A dimension of x0 (apparently it is effectively x256) in width or height will result in the game unpacking a huge sprite. Data is temporarily stored [https://github.com/pret/pokeyellow/blob/05925cba37019d93f1c847015f4fbc1de110c200/sram.asm in bankless portions of SRAM] but it is possible for a buffer overflow when later areas of SRAM are touched. Furthermore, glitch Pokémon with both width 0 and height 0 will typically corrupt the memory even further; exceeding the end of SRAM in the memory map (SRAM ranges from A000-BFFF) and touching C000 and beyond.
Other sprites, including those with a dimension width/height value of 0 can freeze the game, but certain glitch Pokémon including Yellow [[MissingNo.]], {{gdex|Y:191|4 4 (hex:BF)}} and {{gdex|Y:237|4(h4? (hex:ED)}} can corrupt the current battle (an effect known as a [[glitch battle]] not to be confused with a [[glitch encounter system]]) in ways such as corrupting what is on the screen or causing [[glitch audio|glitch music]].▼
▲
==YouTube video==
{{YouTube|UbiYeciV_LE|Krauser912}}
|