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.

Sign up for GitHub

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

Jump to bottom

All Pokemon after Oinkologne (916) have incorrect IDs #863

Open
myoKun345 opened this issue Mar 28, 2023 · 6 comments
Open

All Pokemon after Oinkologne (916) have incorrect IDs #863

myoKun345 opened this issue Mar 28, 2023 · 6 comments

Comments

@myoKun345
Copy link

myoKun345 commented Mar 28, 2023 •
edited
Loading

Looks like something went wrong in PokeAPI/api-data#153, and it has messed up all of the ID's after Oinkologne - it now jumps straight to Dudunsparce which is incorrect according to Bulbapedia.

image
@Naramsim
Copy link
Member

Hmm, ok. It's better to revert?

@Naramsim
Copy link
Member

Naramsim commented Mar 28, 2023 •
edited
Loading

Just in case, i reverted to a version of 15 March.

Can you check if the id error also exists in staging.pokeapi.co?

@jack-skinner-552
Copy link

Hi, I'm also seeing the ID issue. I made a GET API call to staging.pokeapi.co and I'm seeing incorrect ID's there as well.
image
Tinkatink's ID should be 957

This was referenced Apr 14, 2023
Closed
Closed
Closed
Closed
@Naramsim
Copy link
Member

Hi, pokeapi got deployed and the issue came back. I reverted to an old build with correct IDs.

@Naramsim
Copy link
Member

@jack-skinner-552, in your issue you provided a CSV with the correct values. Could you submit a PR with that modifications?

@Naramsim
Copy link
Member

@phalt this is the issue fyi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@myoKun345 @Naramsim @jack-skinner-552