fae6532b8a
Track the work needed to audit and complete encounter data and route ordering across all supported games. Covers automated source exploration, Gen 8+ stub population, ORAS/Let's Go completion, route ordering for Gen 5+, Gen 1-4 ordering audit, and special encounters review. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
title, status, type, created_at, updated_at, parent
| title | status | type | created_at | updated_at | parent |
|---|---|---|---|---|---|
| Explore automated data sources for encounter data | todo | task | 2026-02-10T08:58:47Z | 2026-02-10T08:58:47Z | nuzlocke-tracker-rzu4 |
Research and evaluate automated or semi-automated options for populating encounter data, especially for games where PokeAPI has no data (Gen 8+).
Potential sources to investigate:
- PokeAPI CSV/database dumps — the raw data behind PokeAPI may have more than the REST API exposes
- veekun/pokedex — community-maintained Pokémon database with encounter data
- Bulbapedia / Serebii — structured wiki data that could be scraped (check terms of use)
- pkNX / game data extraction — tools that extract data directly from game files
- Community GitHub repos — search for curated encounter datasets (e.g. for romhack tools, fan wikis)
Goals:
- Determine which games can realistically be populated via automation vs. manual entry
- If a viable source is found, prototype a script/tool to import data into the existing seed JSON format
- Document findings even if no automated approach is viable, so we know what's available
Notes:
- The existing Go tool (
tools/fetch-pokeapi/) could serve as a template for new data fetchers - Output format must match the existing
{game}.jsonstructure (routes with encounters, children for sub-areas)