d0b0f08665
Rewrote route_order.json with correct progression ordering for all 15 version groups (Gen 1-9), validated against encounter data files. Added generate_route_order.py script for reproducible generation and validation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
title, status, type, priority, created_at, updated_at, parent
| title | status | type | priority | created_at | updated_at | parent |
|---|---|---|---|---|---|---|
| Add route ordering for Gen 5+ games | scrapped | task | normal | 2026-02-10T08:58:55Z | 2026-02-11T13:54:47Z | nuzlocke-tracker-rzu4 |
Add route progression ordering in route_order.json for all games that currently lack it. Routes should be ordered to match the typical in-game progression (main story first, post-game after).
Games needing route ordering:
- Diamond/Pearl (could alias to Platinum if progression is similar enough)
- Black/White
- Black 2/White 2
- X/Y
- Sun/Moon
- Ultra Sun/Ultra Moon (could alias to Sun/Moon if similar enough)
- Sword/Shield
- Brilliant Diamond/Shining Pearl (could alias to Platinum/Diamond-Pearl)
- Scarlet/Violet
- Legends Arceus
- Legends Z-A
- Let's Go Pikachu/Eevee (currently aliased to firered-leafgreen — verify this is correct)
Approach:
- Reference Bulbapedia "walkthrough" or "appendix" pages for progression order
- Consider aliasing games that share the same region and route progression
- Mark a clear divider between main story and post-game routes where applicable
- The format is an array of route name strings in
route_order.json, keyed by version group slug
Notes:
- This is primarily manual work — play order guides are widely available online
- Verify route names match exactly what's in the encounter data files (case-sensitive)