FlagBrew / PKSM

Gen I to GenVIII save manager.
GNU General Public License v3.0
1.71k stars 173 forks source link

Bug Report - Changing Status Conditions in Pokemon B/W Corrupts Pokemon Data #1366

Open Afterlyte opened 1 year ago

Afterlyte commented 1 year ago

Describe the bug After editing the status conditions of a Pokemon in the Pokemon Black and White games to Burned (what was tested for me, might happen to others), the Pokemon's data gets corrupted, displays having Pokerus in the party screen, and upon opening the summary causes the game to crash.

To Reproduce Steps to reproduce the behavior:

  1. Go to the Hex editor of a Pokemon in the player's party from a Pokemon Black or White save file
  2. Edit the "Status Conditions" Hex value to Burned
  3. Save and open the game
  4. Observe PKRS label on the party screen
  5. Enter the Summary screen, game crashes

Expected behavior Expected behavior is that the status condition of Burned should be applied, PKRS should not get applied, and the game should be able to function as normal.

Screenshots Folder with images, the first 4 are two pairs of top/bottom screen, showing the corresponding values of Pokerus and Status Conditions respectively after editing

Information about your environment

Additional context Game used is a clean ROM dump of Pokemon White, being run by TwiLight Menu on nds-bootstrap, latest version of both, and the save file is accessed via the Extra Saves function of PKSM. Also, going back and simply removing the Burned status condition from the Pokemon completely reverts the issue and change and the game functions as normal again.

piepie62 commented 1 year ago

Hmmm, that is odd. I'll have to do some testing on that; it appears ProjectPokémon's documentation might have been incorrect.