PokeAPI/pokeapi

base_stat updates through generations

Open

#1325 opened on Oct 28, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (5,191 stars) (1,128 forks)user submission
help wanted

Description

base_stats currently only show the pkmn stats from its most recent change.

ex. butterfree = 395 base stat instead of its original 385.

also means that all gen 1 pokemon are inaccurate to it's now removed 'special' stat

Contributor guide

Tech stack
pythonrest api
Domain
backenddata
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic understanding of Pokemon statsfamiliarity with PokeAPI data structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the current base stat implementation in the PokeAPI codebase, likely in a data model or serializer. Check how generation specific stats are handled in the data source (e.g., the pokeapi/data repo). Examine comments in the issue for suggestions on adding a generation field or a list of stat variants. Look at existing endpoints like /pokemon/{id}/ to see if there's a pattern for handling versioned data.