Moving Q: Appears as Map Corruption? Debug Yellow
Posted by: 44HyXpert
Date: 2017-11-22 10:52:54
The Q in question is actually rather specific, obtained by changing $D162 to be larger than your current team. The result is a Q with a species identifier of FF and everything else at 00. Changing $D162 also does not cause memory corruption on its own, as the "real Q" that keeps the party stable moves down and duplicates / stays in its previous spot.
I wanted to see the game's reaction to having an empty Q duplicated from the "real Q" in the front of the party, with another Pokemon behind it. I thought the only possibilities were blacking out or continuing on, but it actually did neither (and didn't crash, either!).
When I moved the Q to the front of the team, I was able to move around, but the game acted almost as if a map corruption had taken place. Any area off-screen was loaded as glitchy tiles and text, and it filled the background when the start menu was opened, but remained the same underneath. (Upon trying this again, I noticed the game would, at this point, turn off all colliders) Eventually, after 4 steps, the game locked me in a closed tile, not allowing me to move any further, but I was able to collide with the walls around me and I could open the menu, allowing me to enter a battle (by $D058). In the battle, the game showed Q as fainted and I sent out the second Pokemon. After exiting the battle, the game returned to normal, with this effect happening again if I moved 4 steps.
Why does this happen?