Lack of distinction In Evolution and Reminder moves
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1.2k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 21
Description
Sorry If this Is an Invalid Issue but I don't really know the consensus behind It
I'm finding lots of Inconsistencies on reminder moves within moves In the Scarlet and Violet move version group In Pokemon movesets
Reminder moves are listed under the egg move-learn-method with no distinction between them and... actual egg moves. This Is true even for legendaries ( I checked Uxie and Entei )
I expected them to be listed as level 0 or level 1 moves, and could only find It appear as such under Dazzling Gleam In Alolan Ninetales' moves
Evolution moves seem to be consistently listed as level 0 level-up moves. But even so, that doesn't specifically tell you they're learned on evo
Would a new boolean field within move objects In the moves array for If It's evo or reminder, or just entirely new move-learn-method endpoints be a solution?
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
The issue names no repository files or tests. Start by comparing Scarlet and Violet move data for reminder-exclusive and evolution moves, including the cited Alolan Ninetales example, then review how move objects and move-learn methods are represented. Done means the API distinguishes these learning methods consistently and documents the resulting representation.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100