Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gen 3 Pokedex Error #927

Closed
PrometheusG opened this issue Mar 8, 2017 · 3 comments
Closed

Gen 3 Pokedex Error #927

PrometheusG opened this issue Mar 8, 2017 · 3 comments

Comments

@PrometheusG
Copy link

PrometheusG commented Mar 8, 2017

Hi,

When I click on: Seen All and Caught all on PKHeX and importing my Emerald save it is still showing in the pokedex in-game the same amount of seen and caught as before,with no changes.When I try to edit my SAV file again,after first saving in-game, the pokedex tab in PKHeX is being "reseted" like it didn't save the pokemon I clicked from previous edit.
I am using the latest release of PKHeX 2017.03.08

Thanks

@PrometheusG
Copy link
Author

PrometheusG commented Mar 9, 2017

Bonus: It also corrupts the key items with the following error and then alert:
2017-03-09
2017-03-09 1
Oddly enough, it removes some of my key items (The ones deleted are the Basement Key, Devon Scope, Wailmer Pail, Powder Jar, S.S. Ticket, Coin Case, Magma Emblem, Aurora Ticket, Mystic Ticket) :

1)Key items before Checking Seen all, Caught all:
2017-03-09 2

  1. Key Items after saving the file to my cartridge,exporting it with and then opening it again with PKHeX:
    2017-03-09 3

I am using the latest stable version of PKHeX
Thanks

kwsch added a commit that referenced this issue Mar 9, 2017
Were accidentally swapped; fix the underlying cause by reordering to show RS/E/FRLG instead of RS/FRLG/E, because that's how everyone refers to the games (RSE & FRLG).

#927
@kwsch
Copy link
Owner

kwsch commented Mar 9, 2017

I believe it should be resolved now, it was writing to the dex2/dex3 areas for the incorrect game (E <-> FRLG). The item corruption was key in identifying the underlying cause 👍

@PrometheusG
Copy link
Author

Yes it is resolved now,I used PKHeX Build 2163 and it works like charm,thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants