User:ChainSwordCS: Difference between revisions

Jump to navigation Jump to search
Content added Content deleted
No edit summary
No edit summary
Line 10: Line 10:
What happens then? Well, some corruptions can happen. It can affect sprites and OAM (as is common with Yellow Missingno), but it can also go beyond that and corrupt more of the address space. I don't know exactly what's happening in this scenario. Maybe it has to do with sound, or maybe due to a glitch textbox (but I personally find that less likely in this case).
What happens then? Well, some corruptions can happen. It can affect sprites and OAM (as is common with Yellow Missingno), but it can also go beyond that and corrupt more of the address space. I don't know exactly what's happening in this scenario. Maybe it has to do with sound, or maybe due to a glitch textbox (but I personally find that less likely in this case).


====Save States====
Here is a save state for testing: https://cdn.discordapp.com/attachments/549605418192863262/840839746104328192/POKEMON_YELLOW.sn2
* Wild Weepinbell Appeared! (Before . sprite decompression) - https://cdn.discordapp.com/attachments/549605418192863262/840839746104328192/POKEMON_YELLOW.sn2
* An example of OAM being trashed (aftermath) - https://cdn.discordapp.com/attachments/549605418192863262/840873658585972817/POKEMON_YELLOW.sn3


You can load the save state over and over again, and different things happen each time. Sometimes the game crashes, sometimes it's a glitch symphony, sometimes it continues running without a hitch. So whatever is happening is very very likely affected by VRAM Inaccessibility.
You can load the save state over and over again, and different things happen each time. Sometimes the game crashes, sometimes it's a glitch symphony, sometimes it continues running without a hitch. So whatever is happening is very very likely affected by VRAM Inaccessibility.