HGSS Missing PokeWalker Encounters
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- api, backend-api-design
Research direction
Start by reviewing the existing HGSS location, encounter method, and encounter condition data, then compare it with the linked Bulbapedia Pokéwalker areas. Done means the regular Pokéwalker locations, areas, transfer method, and steps, group, and region conditions are represented consistently in the API.
Written by the indexing model from the issue text.
Description
The API is currently missing the PokeWalker encounters from the HGSS companion accessory.
I think this should be supported, first of all, and I would do it in two separate PRs:
- All regular locations
- All event locations
The PokeWalker has its own sub-locations, but whenever a Pokemon caught in it is shown in-game, it just says "pokewalker".
I would propose we add 6 things to include the PokeWalker:
- PokeWalker Location
- Location areas for each PokeWalker area, tied to the pokewalker location: https://bulbapedia.bulbagarden.net/wiki/Pok%C3%A9walker#Areas
- Encounter Method called Pokewalker Transfer
- Encounter condition called "steps" and show the minimum number of steps you need to walk to find that Pokemon.
- Encounter condition called "group x" to note which group the pokemon is a part of. Because some mons are mutually exclusive.
- Encounter condition called "region"
On note 6. The "special" areas include event only areas, and some are japan only. Those I would set those areas to the encounter condition called: region-japan, indicating you need a japanese pokewalker.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1.2k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 18
Getting set up
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.
More from PokeAPI/pokeapi
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PokeAPI/pokeapi#1684 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-2 days Newbie friendliness 76/100
PokeAPI/pokeapi#1631 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
PokeAPI/pokeapi#1623 · 3 comments ·
Maintainers usually reply within 1 day
-
UV hardlink filesOpen
Difficulty 3/5 1-2 days Newbie friendliness 48/100
PokeAPI/pokeapi#1622 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vllm-project/vllm-metal#822 ·
Maintainers usually reply within 1 day
-
vector-store
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
mem0ai/mem0#7461 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: chunk_span_bounds and _validated_chunk_spans reject Pydantic models ChunkSpan and AudioFileOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BasedHardware/omi#19047 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day