Capture rate changes between games
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1.2k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 21
Description
According to this bulbapedia list, the capture rate for many Pokemon has changed both between gens, and between games.
I think this is something the API should support if there's going to be an attempt to have past types, past stats, and past moves.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the API currently represents each Pokémon's capture rate and how it handles historical types, stats, and moves. Compare the model with the linked Bulbapedia list of changes between generations and games. Done means the API has a defined, documented way to retrieve the appropriate capture rate for each game context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100