Install Stars of Destiny
One package, one launcher, two adventures. Set up the randomizer for Suikoden I and Suikoden II HD Remaster.
Stars of Destiny - Character Randomizer · Setup guide · Version 0.14.4 · https://suikodenrand.github.io/guide.html
What you need
- Your own Steam copy of Suikoden I & II HD Remaster on Windows x64.
- An internet connection for the first BepInEx launch, when Unity reference libraries are downloaded.
The full package includes BepInEx 6 IL2CPP x64, Suikoden Fix, the combined randomizer, Windows launcher 1.0.5 and their private .NET runtimes. You do not need a separate loader download, SDK or compiler.
Back up the game’s Save and BepInEx/config folders together outside the game directory. Keep the pair together for each campaign.
Installation
Close the game and launcher
Wait for Steam to show that the game has stopped. Make the paired save and configuration backup first if you already play with mods.
Run the full installer
Download the 0.14.4 setup EXE and run it. The full installer includes the loader, launcher, mod components, offline instructions and required notices. For installation without setup, follow the manual ZIP instructions.
Choose the folder containing
Suikoden I and II HD Remaster.exeandGameAssembly.dll. In Steam, use Manage → Browse local files to find it. Setup checks the supported game build and reports conflicting loader or duplicate plugin files.Choose whether to install ATB
Leave Experimental S1 ATB (installed disabled) unchecked for standard turn-based battles. Selecting it installs the separate preview; it does not enable it. See optional features before turning it on.
Open the launcher and apply your settings
Open Stars of Destiny in the current user’s Start Menu, or run
<game>/StarsOfDestiny Launcher/StarsOfDestiny.Launcher.exe. Choose Suikoden I or II, then set your seed and options. To use a website preset, follow the steps below.With the game closed, select Apply settings or Save & launch game.
Let first-run setup finish
Keep Steam and internet access available while BepInEx downloads reference libraries and generates interop files. The first launch can take several minutes; wait for the title screen.
Start your adventure
Choose the matching game and start New Game to use the new seed, roster, start, weapon and joining-inventory policies. The F6 panel starts hidden; press F6 to cycle its text through Full, Compact and Hidden views.
Upgrading an existing installation
Setup preserves existing settings, campaign bindings, saves and unrelated plugins. Fresh defaults do not overwrite your choices. Leaving ATB unchecked also preserves an ATB installation that is already present. Keep the transaction backup path printed by setup so you can undo that installation later.
Manual ZIP installation
The mod-only ZIP includes the randomizer, complete launcher, Suikoden Fix and dormant optional S1 ATB. It requires BepInEx separately and does not run the setup installer.
- Close the game and launcher and back up
Savetogether withBepInEx/config. - For a fresh mod installation, extract the tested BepInEx 6 IL2CPP Windows x64 build 697 into the game folder, launch the game once to prepare its references, then close it. Keep an already working matching loader.
- Extract the mod ZIP into a temporary folder and read its
START HERE.txt. For an upgrade, followStarsOfDestiny Manual/MANUAL UPGRADE.txt: preserve existing CFGs and campaign sidecars before copying mod files into the game folder. Do not replace an existing configuration folder with fresh defaults. - Keep one randomizer and Fix copy, and at most one active ATB copy if installed. Copy the complete launcher folder, then review and apply your settings with the game closed.
Manual copying does not create an installer recovery transaction. Keep the manual backup and package file list for undo. Activate optional ATB through the launcher only if wanted.
The plugins-only Nexus ZIP supplies plugins, defaults and manual settings instructions without launcher EXEs or a runtime. Install BepInEx separately and edit the CFG files by hand, or add the optional launcher 1.0.5. For a launcher-only upgrade, close the game and launcher, back up the old launcher folder/preferences, then replace its entire folder beside the game EXE.
Use a website settings preset
- In the website settings builder, choose the game, seed, mode, companions, start, joining weapon level and joining inventory, then download the settings preset JSON.
- Install 0.14.4 and open its launcher. Choose Load settings… and select the downloaded JSON.
- Select the game you configured, review its options, then choose Apply settings or Save & launch game while the game is closed.
- Start a New Game in that game.
The preset carries the selected game’s basic campaign choices. The launcher provides the rest of the settings, including dialogue, interface, treasure and optional ATB controls. Loading a preset merges its supplied options; it does not replace your other game’s settings or saved campaign bindings.
Downloading a preset does not apply it. The full installer installs its defaults or preserves existing configurations; it does not read a loose configuration file placed beside the setup EXE.
Seeds & saved games
Suikoden I and II use separate seeds, mappings and settings. Seed, roster, quick start, joining weapon and joining inventory choices apply to new campaigns. Existing randomized saves restore their own seed, cast and weapon policy, including earned sharpening. Saves created before joining-equipment balancing keep their previous inventory policy; upgrading does not replace earned gear.
Starting New Game may replace the shared autosave. Make a manual save and keep a paired backup of Save and BepInEx/config first. Do not delete campaign sidecars to force a different seed or weapon policy onto a saved run.
Ordinary saves are not converted into new randomized campaigns. If a randomized save has lost its binding, restore the matching configuration backup rather than generating a new campaign over it.
Modes, starts & joining weapons
- Character shuffle assigns eligible combat fighters to story roles using your seed. Protagonist shuffle is optional.
- Fixed roster reserves the protagonist and lets you choose five different companions. Story progression still determines how many active party slots are available.
- Random roster uses the seed to choose five companions alongside the protagonist.
Recruitment requirements and story roles stay native. Names, portraits, party and combat appearances follow the replacements; some custom scene animations retain native handling. Supported English dialogue mentions use shuffled names, while ambiguous references, other languages and unsupported messages stay original.
Native shuffled-character Unite previews follow the actual fighters in your party, including replacements occupying unrelated story roles. Participants still need to satisfy each attack’s native conditions. Use normal turn-based battles for these Unites.
| Game | Optional quick start | Fresh joining weapon default |
|---|---|---|
| Suikoden I | Before Viktor joins, at the prepared Gregminster checkpoint. | Tir’s current weapon level at first party join, with seeded −3 to +3 variance. |
| Suikoden II | Viktor’s camp interior, before the first chores. | Riou’s current weapon level at first party join, with seeded −3 to +3 variance. |
The normal opening is the fresh default in both games. Both joining weapon policies can match the protagonist exactly and stay within the legal range. Adjustment happens once; later rejoining and sharpening preserve earned levels. Match original character and Level 1 are also available. Protected setups retain native handling, and Suikoden II’s natural weapons remain level 0.
Joining inventory & equipment
The fresh default in both games is Original role's starting inventory. On a replacement's first party join, it copies the original story character's armor, accessories and carried items, including consumables. Incompatible gear is replaced with comparable equipment the new fighter can wear.
This works with Character shuffle, Fixed roster and Random roster. Choose Replacement's starting inventory to retain the previous behavior. Weapon identity, runes and the separate joining weapon-level option keep their own handling.
The policy is saved with the campaign and applies once. Later joins preserve acquired items and player equipment changes. Existing campaigns keep their saved policy: saves made before this feature retain the previous replacement-inventory behavior. Start a new campaign to use the new default.
Optional features
Suikoden I treasure shuffle
Experimental and off by default. In launcher 1.0.5, tick Enable chest shuffle for new campaigns in Treasure settings before starting a new game. Protected recruitment items, potch and special rewards stay original. Existing saves keep their own chest policy; unchecking the new-campaign option does not pause an existing shuffled save.
To change an existing save, choose checked for shuffled rewards or unchecked for original rewards, select Apply settings, select its snapshot in Saved campaign chest settings, then click Reset selected save’s chest settings. The next load adopts that choice. The manager backs up the old policy; acquired items and opened chest flags stay intact. Applying settings in 1.0.5 also clears a global chest pause left by an older launcher. Suikoden II chest randomization is not included.
Suikoden I active-time battle preview
Open the launcher’s S1 Battle & ATB tab. If ATB is available but not installed, as in the manual ZIP, first disable S1 shuffled Unites and click Activate ATB preview. Skip activation if setup already installed the optional component. Turn off Enable shuffled-character Unite attacks for S1 before enabling ATB. Apply and relaunch. Heroes and enemies use SPD meters, with DEX contributing to enemy charge and randomized opening charge; native command menus and targeting are used.
To return to standard battles, disable ATB, then re-enable shuffled Unites if wanted. ATB and shuffled Unites cannot run together. Suikoden II retains native turn-based combat. Nuzlocke is not included in this package.
Troubleshooting & restore
First launch is slow, or no F6 panel appears
Wait for BepInEx’s first-run reference download and interop generation. Check BepInEx/LogOutput.log for progress or errors. Once in-game, focus the window and press F6: hidden is the default, and visible modes show text without a black box. The launcher can change the startup view.
My seed, quick start or joining equipment did not change
Load the website JSON with Load settings…, apply it in the launcher with the game closed, and start New Game in the selected game. Existing saves keep their bound seed, policy and progress. Upgrades preserve existing configuration choices, so select Riou’s ±3 option explicitly for a new S2 campaign if an older policy was retained.
Setup reports a loader conflict or duplicate plugin
Keep a backup before changing anything. Do not mix different BepInEx core or runtime versions. A renamed folder under BepInEx/plugins still loads its DLLs; duplicate randomizer, ATB or Fix copies must be moved outside that plugins tree. Follow the reported conflict rather than bypassing setup’s checks.
How do I undo this installation?
Close the game and launcher. Open the Start Menu support shortcut or <game>/StarsOfDestiny Setup, then run Restore.cmd. Supply the FullPreview-* transaction backup path printed by setup under <game>/SRR-Backups. Restore checks the current files before reversing one installation transaction. If a later transaction or edit conflicts, follow its message or undo later transactions first.
Restore does not rewind gameplay or undo later settings edits. For a whole campaign restore, use its paired Save and BepInEx/config backup. Launcher configuration backups are under BepInEx/config/StarsOfDestiny.Launcher/backups.
This release includes previews that need wider playtesting, particularly scripted battles and Unite combinations. Riou-based first-join weapon handling has managed test coverage; native playtesting of that new option is pending. Initial S1 joining-equipment and saved-loadout checks passed; broader recruitment and reload testing continues. When reporting an issue, include S1/S2, versions, seed, mode, scene and BepInEx/LogOutput.log.