Hi everyone!
I managed to stumble upon a glitch while catching Spiritomb in Pokémon Shining Pearl.
For some context, I made an attempt at getting a Shiny Spiritomb. At the time of recording, I had completed two gyms, and have, of course, completed the requirement of meeting 32 unique NPC's in the Grand Underground.
Eventually, I gave up on getting a shiny and just caught it at the next reset. However, I didn't really care for its nature, so I decided to reset (or maybe that was just an excuse to try for a shiny again). However, when I reset and started the new match, I noticed that I still had the Spiritomb from before the rest in my party. I caught the second Spiritomb, then realized that it must be related to the autosave feature. I reset again without saving manually, and sure enough, I had one Spiritomb in my party, the second one was in the box, and I was able to trigger another Spiritomb encounter on the third try.
At this point, I decided to plug in my capture card and start recording so I can share this with you all, and that is where the video begins. In the video, I manage to catch two more Spiritombs. I eventually decide to go heal my team before going for another Spiritomb. However, it seems that the autosaves that triggered upon entering and exiting the Pokémon Centre in Solaceon Town reuslted in the crumbling tower's flag finally switching permanently, which is why after catching five Spiritombs, you can see in the video how I can no longer trigger another encounter after the reset.
I did not notice any missing Pokémon from my party of boxes. Sometimes, glitches which mix up the states between different parts of the game (such as cloning glitches) can result in Pokémon being deleted. I did not see anything like that happen thankfully. In the case of the first Spiritomb, reseting after catching it did NOT delete the Pokémon that replaced its spot in the party (which was the Pachirisu you can see in my box in the video).
That being said, if you try this glitch/exploit yourself, please note that I did not test this thoroughly at all. Therefore, I cannot guarantee that this glitch will not result in any issues with your save file resulting from other autosave issues, as clearly, the autosave in this game is flawed.
Lastly, as for why this is occurring, I cannot really tell for certain. At least, I think we can safely say that the autosave feature does not correctly update the state of the Hallowed Tower, at least until you go to another map. This may imply that the autosave skips some data based on where you are, and that perhaps there was an oversight in how the autosave feature determines what data needs to be saved given the player's current location, or after which event the autosave starts (i.e. a battle, entering/exiting a building, etc.). Again, I cannot confirm any of this, but I do invite any other theories you may have!
If you have any questions, feel free to let me know! Thank you for watching!
Информация по комментариям в разработке