Repository navigation
Description
BDSP AutoStory Roadmap 2.0
Draft for discussion • 6 November 2026 • developer-butters
BDSP AutoStory has progressed from route construction to full-run verification. The immediate objective is to complete the existing Outside Help Infernape workflow from Segment 00, through the manual HOME handoff, to a verified final save after Cynthia. Broader starter support, compatibility, recovery, regression testing and release preparation follow with separate acceptance gates.
This roadmap retains five phases, replaces outdated implementation tasks with their current verification requirements, and keeps future unassisted development separate from the current assisted route.
Current baseline
| Area | Current position | Remaining gate |
|---|---|---|
| Story route | Segments 00–09 are registered and the route now reaches Cynthia. Older claims that the later gyms and League are wholly absent are obsolete. | Full-run verification, including cumulative state and every handoff. |
| Champion | User confirmed one Cynthia victory on the first attempt. | Repeat within the complete route and verify ending/restart/final save. One win does not establish a win rate. |
| Ending | 140-second A mash, HOME restart with existing reentry, additional save verification and completion popup are implemented. | Live verification; restart/save failure must stop without replaying the Champion route. |
| Tutorial | Seven checkpoints, including settings verification and the post-catch split; separate Tutorial and Main Story selections. HOME instructions appear at completion. | Verify the requested visible HOME reminder presentation and exact return position; instructions alone do not prove the requested popup is complete. |
| Language | Language selection is exposed and passed into run options. | Complete caller/resource/template localization and test all BDSP languages. |
| Save safety | A reported checkpoint-save failure now raises a terminal error before movement or checkpoint-count advancement. | Failure-path tests, practical save guarantees and unsupported backup recovery. |
| Test configuration | Outside Help Infernape with fixed slots and current League policy. | Preserve this baseline while testing; adopt research changes only as a separate coordinated change. |
| Research and test planning | Detector inventory, localization audit, team/EXP plans and shared-program regression matrix exist. | Implement selected work and collect the required evidence. An inventory or simulation is not a gameplay pass. |
The previous build/offline checks passed according to the development handoff. This roadmap review performs no build or new gameplay test.
Phase 1 Complete and repeat the current full run
Priority: now. Establish a reliable reference run before broad optimization or helper reorganization.
- Record the exact Arduino-Source, Packages and CommandLineTests revisions, including the source working-tree changes. Resolve the read-only Git status problem so the tested source baseline can be identified.
- Review the early Oreburgh searches before testing: Curtis, Diana and the town-tour dialogue loops need bounded failure behavior. Correct the 01.01 gate-side description and specify the Main Story Center position precisely.
- Run Tutorial Segment 00 from the initial bedroom after TV. Verify settings, starter selection, Starly, training/healing, second catch, Pokedex, Town Map, Poketch and the PC endpoint.
- Complete the manual HOME handoff. Return the original-save, evolved level-100 Infernape to party slot 1, with full HP and PP and the exact BDSP destination moveset.
- Verify the additional Pokemon storage contract used by Spear Pillar: the required extra Pokemon is in Box 1 slot 1, retrieval works, and deposits restore the intended party after doubles and optional legendary capture.
- Continue Main Story Segments 01–09. Check position, facing, dialogue, menu state, items, party, Repel, bike/gear, registered items, Poketch, flight unlocks, HM/story flags and save state at each boundary.
- Validate encounters that can trigger or be skipped, including consecutive battles, NPC partners and own-party doubles. A fainted ally must not be mistaken for defeat of the whole party.
- Reconcile PP across healing spans, purchases and actual money, item consumption, new-item flags, Repel movement and reset restoration. Include Coronet retry state, Surf/landing animation waits, Victory Road alignments and Sunyshore move fallback.
- Verify the League and final sequence against the acceptance policy below.
- After each observed failure, preserve the first divergence, correct it with existing helpers where possible, and retest its entry and following handoff. Revalidate downstream assumptions affected by that correction.
Proposed completion gate: one documented complete Tutorial → manual HOME handoff → Main Story → final-save run, followed by a repeat on the same source/resource baseline. Record automatic recoveries, consumable use and any manual intervention beyond the documented handoff. A run with a manual route repair is useful evidence but does not pass the full-run gate.
Use the full-run checklist for the detailed steps and checkpoint inventory. Its 09.10 flight test is a diagnostic inventory entry, not part of the registered production run.
Preserve the current Infernape policy
| Setting | Current implementation to verify |
|---|---|
| Move slots | 1 Thunder Punch, 2 Flamethrower, 3 Earthquake, 4 Brick Break |
| Starting PP budget | 15 / 15 / 10 / 15; full actual PP required at startup |
| Shopping | Reach stock levels of 3 X Attacks and 10 Full Restores; buy the deficit |
| Aaron | Confirm actual species; Thunder Punch against Beautifly and Vespiquen, Flamethrower against the others |
| Bertha | One X Attack against Quagsire |
| Cynthia | Two X Attacks against Spiritomb; Full Restore takes priority below 60% HP; cap four in-battle Full Restores |
| PP accounting | Items consume no attack/PP; Pressure charges two PP per attack into Spiritomb; Full Restore does not refill PP |
| Between members | Read exact HP in Bag; use Full Restore when HP is missing and recheck |
| Champion approach | Doorway fade triggers automatic introduction; no extra room approach input |
| Finish | 140-second A mash → HOME restart/reentry → verified additional save → “Congratulations! Autostory Complete!” |
| Final failure | Stop without retrying Cynthia against the postgame save |
The separate all-starter audit proposes larger X-item/healing budgets and different lookups, including an Aaron choice that conflicts with the current Vespiquen policy. Those proposals do not override this baseline.
Phase 2 Harden setup recovery and supported behavior
Priority: current correctness before broad beta. Apply the appropriate checks to ordinary segment starts and direct checkpoint starts.
Startup and options
- Validate selected ranges, stale saved selections and meaningful start/end ordering. Keep descriptions next to the correct selections and avoid exposing editable run options whose changes the runner ignores.
- Verify required game settings, including Autosave OFF persistence, battle style, language and clock/time-sync prerequisites. Preserve the date when setting the established 13:00 lighting setup and allow lighting to settle where required.
- Before Main Story movement, verify starter species/evolution, level 100, slot 1 and exact move order. Include readable errors such as “do you have your starter maxed and in slot 1?” Verify HP/PP readiness rather than silently treating a partially used direct-start save as full.
- State actual stat, nature, IV/EV, held-item and PP-Up assumptions. The ordinary assisted contract should not silently acquire optimized-stat requirements from a simulation.
- Finish the tutorial HOME reminder and instructions, including the required party/Box setup and exact return location.
- Audit every exposed option. Verify Catch Box Legendary behavior and post-capture deposit; resolve the still-unpassed Shiny Starter selection through implementation and tests, or explicitly remove an unsupported choice from the release interface.
- Keep No Outside Help identified as unfinished until its separate route is implemented. Current common route blocks must not be accidentally skipped by premature help-mode conditions.
Recovery and diagnosis
- Audit every checkpoint save/retry contract, especially save=false callers. Implement a validated recovery policy or stop explicitly; reload_backup_save remains a no-op in the reviewed source.
- Test save refusal/timeouts, reentry failure, cancellation, exhausted attempts, unavailable resources and invalid setup. Route actions must not execute from an older or unknown save after an entry-save failure.
- Count actual game resets separately from failed attempts. The reviewed wrapper increments the reset counter before confirming a reset, including terminal attempts.
- Include checkpoint name and start-state context in attempts, terminal failures and recoverable notifications. Wire repeated-failure reports and screenshots using established program conventions.
- Bound remaining searches/waits and check ignored flight, heal, Bag, shop and battle results. Distinguish deterministic setup/resource faults from transient failures worth retrying.
- Handle fainted lead, forced replacement, ally fainting, full-party defeat, unexpected battle layouts and return to overworld explicitly.
- Audit existing grass/escape diagnostics before adding logs. Preserve useful stage evidence for transition detection, command selection, escape and overworld return.
- Test the ending's success popup, error classification, completion notification and any Go Home When Done behavior together. Preserve the required popup and no-replay rule while reconciling SV program conventions.
Route and resource accounting
- Complete and verify assisted Torterra and Empoleon support after the Infernape baseline, including tutorial performance, starter-specific rival teams, exact moves/PP, League lookups and shopping. All advertised assisted starters must pass the release matrix; choosing the more elaborate research strategies is a separate decision.
- Maintain one supported slot/PP/battle-plan contract per starter. Check immunities, both ability fields, contact/status risk, spread damage to allies, Sturdy/Sash, actual send-out order, extra hits and Pressure.
- Validate HP and PP reading regions, complete numeric parsing, plausible ranges and uncertain readings. Refilling tracked PP requires confirmed healing/reload; consuming an item must not advance an attack sequence.
- Audit deterministic trainer plans and the requested “repeat the final specified move” behavior after a sequence ends. Keep post-battle dialogue cleanup explicit at callers.
- Reconcile wallets at shopping checkpoints from actual fights and spending. Optional encounters are conditional income; retries do not earn a trainer prize twice after a save reload.
- Verify late-game Bag search, arbitrary starting pockets, empty pockets, changing item rows, quantities, purchase completion and new-item flag clearing.
- Apply movement-only Repel budgets of 12/22/30 seconds for Repel/Super/Max. Exclude menus, waits, dialogue and battles; reset after successful activation. Avoid premature forced expirations and restore alignment after expiry movement.
- Audit building-entry searches while approaching/alignment, cancel outdoor movement on transition, wait for visibility and confirm the intended interior. Recognize an already-visible interior. A fade alone does not identify a destination.
Completion gate: invalid setup fails before route movement; supported checkpoints recover from known saved states or stop clearly; accounting and notifications describe what actually happened.
Phase 3 Complete compatibility tests and focused cleanup
Priority: required release work. Shared-code coverage can proceed alongside route verification.
Language and capture compatibility
- Finish all-language support through callers, dictionaries, text-bearing templates and settings verification. The dropdown is complete; multilingual behavior is not.
- Reuse canonical item/species/move tokens and existing OCR infrastructure. Seed from exact BDSP text and compatible existing dictionaries, then validate against BDSP screens.
- Cover shop/Bag items, Repel types, settings labels/values, operational prompts, move names, prices/stock/quantities and required battle text. Audit missing OCR backend models and packaged dictionaries at startup.
- Use stable encounter IDs plus route context; localized trainer names/classes are supporting evidence and may be duplicated. Reject ambiguous species/number readings.
- Include Japanese text-mode variants where relevant. Distinguish language-independent geometry from templates that contain localized text.
- Test early/late menus, both character Bag appearances, banners/new-item flags, empty/occupied boxes, singles/doubles, white HP text and negative screens.
- Validate capture resolutions, shadows/lighting, controller timing, Switch 1/2 and supported desktop platforms. Start color robustness work with controlled settings changes; label simulated variation separately from independent capture hardware.
- Validate every starter in the tutorial before assuming level-100 Main Story testing covers it. Reproduce relevant reports from dayfine as focused cases, without importing assumptions from an unassisted run into the assisted specification.
Inference and other program regressions
- Refresh the branch detector inventory against its actual base and dirty source. Include inference embedded in helpers, not just files named Detector.
- Every changed detector/inference implementation needs meaningful positive and negative screenshot tests. Retain original failures, ordinary supported screens, resolutions and opt-in/default-mode distinctions.
- Preserve the tested menu fallback stripe shift and short-dialog behavior unless new evidence warrants a change. Reuse both fixture sets, three resolutions and both menu-banner modes where applicable.
- Execute all 12 program rows in the shared-code regression matrix: Autonomous Ball Thrower; Fishing, Overworld and Shaymin hunting; Doubles Leveling; Legendary Reset; Starter Reset; Route 210/212 Money Farmers; Egg Autonomous; Gift Berry Reset; Activate Menu Glitch v1.1.2.
- Cover Shiny Encounter Tester, Unit Test Runner/command-line registration and AutoStory/Lighting diagnostics. Keep unavailable version-specific tests pending with a reason.
- Refresh direct and indirect consumers whenever a shared implementation changes, and rerun affected programs. An AutoStory win or successful build cannot substitute for those tests.
Cleanup and release preparation
- Remove release diagnostic controls and execution/configuration paths, including fake saves and obsolete post-catch controls. Test legacy hidden settings cannot activate them. Retain useful automated regression tests.
- Review temporary panels, experiments, stubs and dead code against current callers. Older requests to remove dialogue utilities must be rechecked because clear_dialog now has working callers.
- Audit helper overlap and migrate callers in focused changes. Preserve tutorial-specific cases and route blocks in their segments; proposed Battle/Navigation/Bag filenames are not settled requirements.
- Keep wrappers responsible for saves/retries and compose one or more named route blocks. Preserve the newer checkpoint split and saved-selection migrations.
- Batch names, endpoint wording, comments, duplicate route notes and formatting cleanup after behavioral boundaries are correct. Preserve each file's line endings, four-space continuation indentation and no tabs.
- Coordinate source, Packages assets, fixtures, OCR models and wiki. Check casing, missing resources, licenses/attribution, and reproducibility without local-only files.
Completion gate: supported compatibility paths and changed inference are covered; all applicable shared-program tests pass; release configuration excludes diagnostics; source/resources/tests reproduce from identified revisions.
Phase 4 Complete beta review and release
The history already records WIP PR PokemonAutomation#1717. Refresh its current state and reviewer requests before planning another draft. Early architectural review and focused contributions may proceed before the final reliability gates; final merge remains gated by them.
- Reconcile outstanding maintainer feedback, keeping detector changes independently reviewable with callers, resources, tests and evidence.
- Align program orchestration, options, checkpoint contracts, statistics, startup checks, reports and completion behavior with current SV patterns where practical. Document BDSP-specific reasons for retained differences.
- Update the wiki and collaborator onboarding: exact setup/HOME moves, Box contract, start/end positions, manual steps, language/platform support, recovery limits and tested revisions.
- Run a clean-checkout build, required CI and affected tests using matching source/Packages/CommandLineTests revisions.
- Execute a beta matrix covering all advertised starters/options/languages, normal and advanced starts, retry boundaries and capture/controller setups. Record incomplete cells explicitly.
- Define release evidence: run count, automatic resets, manual interventions, recurring failure classes, time and consumables. Agree the beta run count before claiming repeatability.
- After authorized focused merges/rebases, reassess changed dependencies and invalidate affected prior test results.
- Complete a readiness review against Phases 1–3 and the declared support matrix.
Completion gate: reproducible delivery, required validation and maintainer review are complete, documentation matches behavior, and remaining limitations are explicit. Commit, push, PR edits/creation, branch changes and publication still require the user's request.
Phase 5 Develop selected future capabilities
These are separate workstreams with their own designs and acceptance criteria. They should not displace the current full-run baseline.
| Workstream | Next work and dependencies |
|---|---|
| Alternative assisted starter plans | Required Torterra/Empoleon support belongs in Phases 2–4. Separately evaluate the larger all-starter research plans, actual-stat gates and zero-Ether/Elixir strategies. Coordinate any Brine versus Metal Claw change across preparation, slot-4 capacity, fallback rules, wiki and tests before adopting it. |
| Conservative League alternatives | Compare larger X-item/healing plans with the proven Infernape baseline. Select one coherent plan per configuration; avoid mixing stock lists, foe lookups or blackout/reload policies from incompatible drafts. |
| No Outside Help route | Preserve existing pathing where practical and minimize detours; no Underground. Develop captures, training, item/TM pickups/sales and money requirements for the fuller team. |
| Kazza and team progression | Verify acquisition, shared/traded EXP, real trainer crossings, obedience limits, boxing/retrieval and Eterna Forest training with Cheryl. Measure the finalized route before optimizing; keep box access with Cheryl verified rather than assumed. |
| Unassisted move preparation | Retain Veilstone Bulldoze and Celestic Surf teaching options; add selected TMs, Heart Scale/Move Reminder, Ice coverage and necessary pickup/return paths. Teaching changes slots, PP and retry state. |
| Team League recovery | Design six-member move/switch/X-item/heal priorities, revives, full wipes, money loss and restocking. A blackout-and-retry plan consumes resources; it is distinct from checkpoint reload restoring inventory. |
| Area recognition pilot | Evaluate AutoMusic-style banners as an additional transition check. Begin in observation mode; handle unknown/ambiguous/missing banners, stale state after resets and localized assets. Area identity cannot prove exact position or facing. Discuss new helpers before implementation. |
| Movement optimization | After reliable route validation, trim excess grass travel and duplicated recorded movement; preserve alignment margins and post-encounter handoffs. Evaluate moving-NPC recognition only where existing geometry/encounter handling is insufficient. |
| Separate development tools | Retain the collision/movement validator and standalone battle/team simulator as optional tools. Audit trainer/immunity exports and model assumptions before relying on them. |
Completion gate for each selected upgrade: agreed scope and support contract, dependency review, focused implementation, meaningful tests and gameplay evidence before entering the ordinary route.
Working rules and evidence
Source edits may proceed while live; builds require SerialPrograms closed. Never inspect new logs/video, recording status or recordings until fresh explicit confirmation that both run and recording have stopped. Historical monitoring instructions do not authorize monitoring now.
Reuse existing helpers; discuss entirely new helpers first. Prefer walls, signs and stationary NPCs for alignment. Standard D-pad timing is 80 ms pressed / 300 ms released, with repeat_dpad facing behavior where enabled. Preserve human edits and line endings; use cmd.exe; do not commit, push or change branches without a request.
For each validation, record source plus dirty patch/hash, resource/test revisions, configuration, game language/version, capture/controller/platform, scenario, expected/actual result and evidence location. A later implementation change invalidates the affected earlier result.
Full run verification checklist
Prepared 2026-11-06. Attribution: developer-butters.
Scope and evidence boundary
Read the live Arduino-Source AGENTS.md, CONTRIBUTING.md and CodingAgentContext/AutomationProgramPatterns.md. Source-only review; no run evidence, recording status, application status, build, tests, source edits, commits, pushes or branch changes. Branch query returned BDSP/AutoStory. Git status failed with a work-tree error; existing-edit baseline remains unverified. Previous successful build/offline checks and Cynthia victory are user-provided history, not newly verified results.
PRE-FLIGHT
- Use Tutorial, Segment 00 (or advanced 00.00 through 00.06). Start in the initial bedroom after TV stops, matching the displayed start description.
- Select Chimchar and Outside Help; confirm language matches the game.
- Diagnostic fake checkpoint saves OFF for normal full-run verification. Fake mode replays the entire selected range after reloading its initial save.
- Verify required game settings at 00.00; failure must stop before route movement.
- Preserve the original starter identity for the return through HOME; retain the second caught Pokemon during transfer.
- If a build becomes necessary, obtain confirmation that SerialPrograms is closed first.
TUTORIAL AND HOME HANDOFF
- 00.00 settings verification; 00.01 bedroom to Lake Verity; 00.02 Chimchar selection and Starly fight.
- 00.03 Pokedex; 00.04 second Pokemon caught and catch sequence finished; 00.05 arrival in Jubilife; 00.06 Town Map/Poketch and Pokemon Center PC position.
- Tutorial finishes separately and displays the HOME transfer instructions. It does not continue automatically into Main Story.
- Deposit starter, save/close BDSP, perform HOME preparation, return fully evolved level-100 Infernape to party slot 1.
- Exact slots: 1 Thunder Punch, 2 Flamethrower, 3 Earthquake, 4 Brick Break. Full HP and PP before Main Story starts.
- Return to the intended Jubilife Center PC position, close menus, preserve expected facing. Segment 01 begins with recorded movement from inside the Center; its start description alone is insufficient to specify position.
- Select Main Story, Segments 01 through 09 (or checkpoints 01.01 through 09.09). Recheck settings after changing story section.
SOURCE REVIEW FINDINGS / LIMITS
- Segment registration includes 00 through 09; tutorial registers seven checkpoints 00.00 through 00.06. Main Story starts after those seven. Manual flight test 09.10 is not registered.
- Segment boundary descriptions agree from badge 3 onward: Maylene facing north -> Pastoria doorway facing south -> Hearthome post-Cynthia -> Canalave entrance -> Snowpoint doorway facing south/Repel inactive -> Sunyshore doorway. First/second badge descriptions are less specific; verify actual position, facing and cleared dialogue during the run.
- Checkpoint 01.01 end text says outside Oreburgh Gate on the Jubilife side. Its body calls jubilife_to_oreburgh_gate then oreburgh_gate_nav, which traverses the gate and detects its exit. Treat the side label as a likely stale description; do not manually resume based on it without checking actual position. No correction made in this source-only pass.
- oreburgh_gate_nav repeats walking/dialogue checks for Curtis and Diana without an outer attempt/time limit. A missed trigger could keep this checkpoint moving indefinitely. Later oreburgh_gate_to_mine has a similarly unbounded tour-dialogue search. These are static risks, not observed new-run failures.
- Startup initializes Infernape PP budgets to 15/15/10/15 and assumes full actual PP. Real checkpoint reload restores the captured PP balance; reviewed healing code refills tracked capacity. Full Restore restores HP/status, not PP. No full-route numerical PP sufficiency proof has been completed.
- Reviewed League plans match requested species-based move selection, setup items, healing threshold, and stock targets. Success still depends on cumulative money, inventory, PP, party and route state from the full run.
- Ending uses 140 seconds of A mash, HOME restart/reentry, save verification, and the completion popup. Post-Hall-of-Fame failures are promoted to fatal exceptions to avoid checkpoint retry. The success popup also uses FatalProgramException: judge completion by its exact message and verified final save, rather than a generic success notification. Ending remains live-unverified.
CUMULATIVE ROUTE CHECKS (review after explicit confirmation BOTH run and recording stopped)
- At each checkpoint: entry position/facing, menus closed, dialogue finished, save verified, exit handed directly to next checkpoint.
- Record first divergence, checkpoint ID, expected/observed state, recovery result and whether a reload actually occurred.
- Confirm heal events restore actual and tracked PP together; PP deductions follow attacks and Pressure; item turns do not count as attacks.
- Verify money is sufficient at each purchase, target-stock calculations use existing inventory, and required items remain available later.
- Track bike/gear, registered items, Poketch state, Repel state/expiry, flight unlocks, partner/double-battle party assumptions, HM/story flags and rewards.
- Pay special attention to long stretches with no healing, noncontact-only move restrictions, Coronet reset state and Sunyshore slot 3 -> slot 2 PP fallback.
- Prefer existing walls, signs and stationary NPC alignment when a route correction is needed. Standard D-pad 80 ms pressed/300 ms released; reuse repeat_dpad where enabled. Discuss entirely new helpers first.
LEAGUE ACCEPTANCE
- 09.04 rival defeated, healed, shopping finished; stock targets 3 X Attacks and 10 Full Restores, buying only the deficit.
- Aaron: species confirmed; Thunder Punch against Beautifly/Vespiquen, Flamethrower against others.
- Bertha: exactly one X Attack against Quagsire before planned attacks.
- After each Elite Four fight: exact HP read in Bag; Full Restore only if HP missing; recheck succeeds before moving on.
- League PP carries across fights; no PP refill credited for Full Restore. Confirm remaining budget before Cynthia.
- Cynthia doorway triggers automatic intro, with no extra room movement/A interaction after fade.
- Cynthia: two X Attacks against Spiritomb; heal first below 60% HP; maximum four in-battle Full Restores; two PP per attack into Spiritomb, zero PP for items.
- Cynthia species moves: Spiritomb/Milotic slot 1, Roserade slot 2, Gastrodon/Garchomp slot 3, Lucario slot 4.
- HP/opponent recognition failure stops rather than selecting an unconfirmed action; healing must show improvement after the opponent turn.
- Victory -> 140-second A mash -> HOME restart using existing reentry -> additional save verified -> exact popup Congratulations! Autostory Complete!
- Restart/save failure stops without retrying Champion against a postgame save.
EVIDENCE REVIEW GATE
No assumption has been made that a run or recording started. Before opening ANY new logs/video/screenshots or checking recording status, obtain fresh explicit user confirmation that BOTH the run AND recording have stopped. After that confirmation, identify the exact evidence set before reviewing it. Existing named evidence folders and the previously reviewed video were not accessed in this pass.
CHECKPOINT INVENTORY (from live source; descriptions are contracts, not proof)
Segment 00
- 00.00 - Verify Settings
- 00.01 - After TV
- 00.02 - Outside Verity before starter
- 00.03 - Outside Verity after starter
- 00.04 - After Pokedex
- 00.05 - Route 202 after catch to Jubilife
- 00.06 - Jubilife to Poketch
Segment 01
- 01.01 - Maxed Starter from Home
- 01.02 - Oreburgh Mine
- 01.03 - Oreburgh Gym
Segment 02
- 02.01 - Outside Gym 1
- 02.02 - Floaroma Town
- 02.03 - Route 205 to Eterna Forest
- 02.04 - Eterna Forest
- 02.05 - Eterna City to Gym
- 02.06 - Inside Gym
Segment 03
- 03.01 - Eterna Gym to Jupiter
- 03.02 - Jupiter to Mount Coronet
- 03.03 - Mount Coronet
- 03.04 - Coronet to Hearthome
- 03.05 - Hearthome to Lost Tower
- 03.06 - Lost Tower to Veilstone
- 03.07 - Veilstone Gym (start inside at entrance)
Segment 04
- 04.01 - Veilstone recovery
- 04.02 - Galactic grunts and Fly
- 04.03 - Route 214 and Valor Lakefront
- 04.04 - Route 213 to Pastoria
- 04.05 - Pastoria Gym and Wake
Segment 05
- 05.01 - Pastoria recovery
- 05.02 - Galactic chase and Solaceon
- 05.03 - Route 210 to Celestic
- 05.04 - Celestic story and Hearthome
- 05.05 - Hearthome Gym and Cynthia
Segment 06
- 06.01 - Hearthome to Jubilife
- 06.02 - Jubilife to Canalave
- 06.03 - Canalave rival battle and healing
- 06.04 - Canalave Gym and Byron
Segment 07
- 07.01 - Canalave library events
- 07.02 - Canalave to Route 216
- 07.03 - Route 217, Snowpoint Mart and Veilstone
- 07.04 - Lake Valor and Saturn
- 07.05 - Lake Verity, Mars and Snowpoint
- 07.06 - Snowpoint restock and healing
- 07.07 - Snowpoint Gym and Candice
Segment 08
- 08.01 - Snowpoint recovery
- 08.02 - Lake Acuity and Veilstone
- 08.03 - Galactic Warehouse
- 08.04 - Galactic HQ and Eterna
- 08.05 - Eterna to Spear Pillar
- 08.06 - Spear Pillar and Veilstone
- 08.07 - Route 222 to Sunyshore
- 08.08 - Volkner at the lighthouse
- 08.09 - Sunyshore Gym
Segment 09
- 09.01 - Sunyshore recovery
- 09.02 - Route 223 and Victory Road
- 09.03 - Victory Road traversal
- 09.04 - League preparation and admission
- 09.05 - Aaron
- 09.06 - Bertha
- 09.07 - Flint
- 09.08 - Lucian
- 09.09 - Cynthia and Hall of Fame
- 09.10 - Fly destination test
Activity
Python: basic pybind11 interface to the microcontroller (PokemonAutom…