Link up --physical and --special Z moves to complete their data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1.2k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 21
Description
The moves between 622 and 657, Z Moves, are usually identical to one another.
For example 623 is effectively the same as 622, with the only real difference being that one is physical, the other specia. I've not played S/M which is where I think this comes from - but I can understand the rational here.
The problem is that for the moves in that range id + 1 has Dummy Data in all of its Flavour Text entries. Could these be combined for completeness?
I also wanted to ask about the learned_by_pokemon fields on those moves (GMax as well). Is that data that's simply not been populated yet because of the sheer volume, or is this by choice? If every Pokémon of a certain type can temporarily use those?
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 inspecting the API data for move IDs 622–657, comparing the physical and special Z Moves and their flavour-text entries. Check the learned_by_pokemon fields for these moves and GMax moves, then confirm whether the requested links and data population are intended before validating the affected API responses.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100