Panludia
COMMUNITY INTEGRATION
Spirit ValleyArchipelago randomizer mod
Explore Spirit Valley, complete missions and battles, register species and their rare variants, and optionally raise affection through five check ranks. Multiworld rewards supply inventory items, quest tools, merchant stock and waystone destinations.
Maintained by DotsofdarknessArchipelago
- Reviewed build
- 2.1.0
- OS
- Windows
- Last reviewed
- 13 Oct 2026
- Installation
- Manual installation
How the game changes
- 485 shuffled checks by default; 863 possible reward entries include 75 ordinary species, 75 rare variants, 375 optional affection ranks, missions, battles, chests and waystones.
- 146 reward types: consumables, crystals, equipment, quest tools, coins, 24 merchant-stock unlocks and optional waystone coordinates. Inventory rewards are processed on location departure or loading.
- Four goals: the main mission finale, all 75 species, all 75 rare variants or affection level five for every species.
- Randomize encounters, trainer teams, moves, evolutions, spirit types and stats, move data, effectiveness and map connections independently. Default encounters and trainer teams are randomized; the other deep randomizers are off.
Before you start
- The referenced release, APWorld manifest and delivered plugin all identify 2.1.0. Install its matching BepInEx client beside SpiritValley.exe and the APWorld in Archipelago; the manifest does not state a minimum Archipelago version.
- Keep a separate or backed-up save: the maintainer explicitly warns that save corruption cannot be ruled out. No native game session or exact game-build compatibility test was performed.
- Three inspected combinations have different pool and constructed-check counts: non-randomized spawns with a collection goal, Single Catch, and the affection goal with spirit checks initially disabled. These are static findings, not full-seed generation or runtime tests.
- Several World warp rules use internal map IDs inside coordinate-item names, while the generated rewards use display names. The client activates destination flags, but those logical warp routes do not consistently match the available items.
- The client’s completion method sends the victory status, but its final goal-location branch repeats the rare-goal condition and does not send the separate affection goal check.
- The goal option is mislabeled as map rando option in the source; this page names it Goal. The map constraint default is Some despite conflicting option prose.