SRAM glitch: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
No edit summary |
(Moved the steps of clearing the save file to the "procedures" section, since the expanded party is the most common reason to do this glitch.) |
||
Line 5: | Line 5: | ||
The glitch exploits a quirk in the code for saving the game to get a save file with a correct checksum. The necessary timing for the hard reset is very precise (less than 0.1 second), but it is still much easier than getting the correct checksum by chance. |
The glitch exploits a quirk in the code for saving the game to get a save file with a correct checksum. The necessary timing for the hard reset is very precise (less than 0.1 second), but it is still much easier than getting the correct checksum by chance. |
||
==Procedure== |
== Procedure == |
||
=== Clearing the save file === |
|||
⚫ | |||
This glitch can be executed at any point in the game, but is most often done at the very start of a new game to access an expanded party. For this purpose, the player needs to clear any existing save files: |
|||
⚫ | |||
⚫ | |||
#* The timing is version-dependent and is easier on {{Y}}. |
|||
# Choose "Yes" to the "Clear all saved data?" prompt. |
|||
Even if the player does not have an existing save file (e.g. on a fresh cart), it is still recommended to clear the save file anyway. Clearing the save file will set the SRAM to all 0xFF bytes, which guarantees that this glitch will give the player an expanded party. On the other hand, the contents of uninitialized SRAM is unpredictable: There is a good chance it will be 0xFF anyway, but it can also be something else. In particular, some emulators initialize the SRAM to 0x00, which means even if this glitch succeeded, it will '''not''' give the player an expanded party. |
|||
⚫ | |||
=== Save corruption === |
|||
⚫ | |||
The following steps can be done at any point in the game. |
|||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | If the glitch was successful, a Continue option will be present when the game is started again, but the player's party will be replaced by the existing party data in the SRAM. In particular, the player will be able to access their Pokémon screen even if they never received the starter (unless the party data in the SRAM had 0 Pokémon). |
||
⚫ | |||
There are two ways the glitch can fail: |
|||
⚫ | |||
⚫ | |||
* If the Continue option does appear, the player may find their party data unchanged (if the player never received the starter in this game, then the Pokémon screen cannot be accessed), which indicates that either the reset happened too late, or the player didn't set up the SRAM data properly (see [[#Clearing the save file|Clearing the save file]] above). |
|||
⚫ | |||
⚫ | |||
==Variants== |
==Variants== |
||
Line 26: | Line 32: | ||
{{Main|255 Pokémon glitch}} |
{{Main|255 Pokémon glitch}} |
||
By performing the SRAM glitch while the player has no save file, the party data will become whatever is in the SRAM, and is likely to be all 0xFF bytes (in particular, clearing the save file will set the SRAM to all 0xFF). As a result, the player will have 255 Pokémon in the party. When the player opens the party screen, it will appear to show nothing in the party, but the player will be able to scroll the cursor to any of the 255 slots and switch Pokémon around. |
By performing the SRAM glitch while the player has no save file, the party data will become whatever is in the SRAM, and is likely to be all 0xFF bytes (in particular, clearing the save file will set the SRAM to all 0xFF). As a result, the player will have 255 Pokémon in the party. When the player opens the party screen, it will appear to show nothing in the party, but the player will be able to scroll the cursor to any of the 255 slots and switch Pokémon around. |
||
⚫ | |||
<!-- Should these be listed on the 255 Pokemon glitch page instead? --> |
<!-- Should these be listed on the 255 Pokemon glitch page instead? --> |