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

Hisui Starter Trio Move compatibilities used in base forms

Open
#1,370 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
api, database

Research direction

Start by tracing the dataset source for Decidueye, Typhlosion, and Samurott and compare the listed base-form move compatibilities with their Hisuian forms. Confirm whether the discrepancy is in PokeAPI or upstream Veekun data; it is done when those incorrect moves no longer appear for the base forms.

Written by the indexing model from the issue text.

Description

data-missing/inaccurate

First of thank you for this database
I am using PokeApi in a project to check and validate movesets of pokemon, which works great.
I do notice however that specifically decidueye, samurot and Typhlosion (their base forms)
seem to mistakenly include TM/Tutor compatibility for their respective hisuian forms when pulled from the dataset

which is to say that the 3 forms have the following move compatibilities reported they shouldn't have:
decidueye: Scary Face, Rock Tomb, Brick Break, Bulk Up, Taunt, Aura Sphere, Reversal, Focus Blast, Focus Punch, Coaching, Upper Hand
typhlosion: Confuse Ray, Hex, Night Shade, Calm Mind, Spite, Poltergeist
samurott: Snarl, Dark Pulse, Lash Out, Throat Chop

as near as i could determine no other species with a regional form (hisuian or otherwise) has this issue only the species of the hisuian starter trio

apologies if this issue is sourced further upstream with veekun's data but i couldn't confirm whether the issue lies in that data or somewhere here

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

Contributor guide

Open the contributing guide

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.