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.3 KiB
1.3 KiB
title, status, type, created_at, updated_at, parent
| title | status | type | created_at | updated_at | parent |
|---|---|---|---|---|---|
| Complete ORAS and Let's Go encounter data | todo | task | 2026-02-10T08:59:09Z | 2026-02-10T08:59:09Z | nuzlocke-tracker-rzu4 |
Omega Ruby, Alpha Sapphire, Let's Go Pikachu, and Let's Go Eevee have minimal stub data that needs to be completed.
Current state:
- Omega Ruby: 96 lines (stub — likely just a skeleton)
- Alpha Sapphire: 96 lines (stub — likely just a skeleton)
- Let's Go Pikachu: 134 lines (minimal)
- Let's Go Eevee: 134 lines (minimal)
Approach:
- ORAS: These are Gen 3 remakes. Emerald data could be used as a base, but ORAS added new areas (Mirage spots, soaring encounters), DexNav encounters, and different encounter tables. Supplement from community sources.
- Let's Go: These are Gen 1 remakes with simplified mechanics. FireRed/LeafGreen data could serve as a base, but encounters are different (no wild battles in traditional sense, overworld spawns). Version exclusives differ between Pikachu and Eevee versions.
Checklist:
- Review and complete Omega Ruby encounter data
- Review and complete Alpha Sapphire encounter data
- Review and complete Let's Go Pikachu encounter data
- Review and complete Let's Go Eevee encounter data