Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unonw-A is missing a bunch of sprites

Open
  • Is something wrong?
#1,687 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
api

Research direction

Start by comparing the responses from pokemon/201, pokemon-form/201, and pokemon-form/10001, then inspect the repository's data source and the change referenced by #1681. Done means unown-a has complete, correct sprite data and pokemon/201 exposes Unown A artwork consistently with the other forms.

Written by the indexing model from the issue text.

Description

Describe the Bug

Of all the unonw forms, on unown-a (pokemon-form/201) is missing sprite data. It only has two backsprites, all other fields are null.

The interesting part here is, that all other forms (pokemon-form/10001 and above) do have full sprite data available. unown-a is the default for, so one could argue that is no problem, as the pokemon resource should have all sprites of that one as well. However, the unown pokemon resource (pokemon/201) is inconsistent in that manner. It does have sprite data, and most of the point to unown-a images, but the artworks for example are of unown-f, not a, meaning there is currently no way to get the A-Artwork via the API, even though all the others are available.

Note: I did not look into it yet, but that might have to do with #1681 . @FallenDeity may you can confirm whether that is a preexisting issue or a problem introduced by your change?

Steps to Reproduce
  • GET https://pokeapi.co/api/v2/pokemon/201 -> Artwork is Unown F
  • GET https://pokeapi.co/api/v2/pokemon-form/201 -> Artwork is missing
  • GET https://pokeapi.co/api/v2/pokemon-form/10001 -> Artwork is Unown B
Resolving the Bug

Anyone is open to making a PR for this issue.

Dominant language
Python
Stars
5.4k
Forks
1.2k
Avg merge
2d 7h
Merged PRs (30d)
17

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PokeAPI/pokeapi

All issues in PokeAPI/pokeapi

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.