Repository navigation
FAQ
Irongoon is a randomizer mod for Severed Chains. Its original ruleset emphasizes difficulty, restrictions, and campaign seeds that are not guaranteed to be completable, but the configuration can also be used for less restrictive randomizer runs.
The work-in-progress Irongoon ruleset is available here
This wiki tracks Irongoon main.future, currently packaged as v0.5.1. Its rolling Latest Irongoon Future prerelease includes matching Severed Chains main.spike-testing builds. Use the release notes for exact source revisions; rolling assets change when new builds publish.
Follow the installation instructions for a matching Future bundle or mod-only installation. The official SC development updater can replace the bundled engine with an incompatible build; it does not update Irongoon.
Profiles are saved at mods/irongoon/configs/<name>-ig.yaml. mods/irongoon/config.yaml is the Legacy fallback when no profiles are found; the old mods/irongoon/US data directory is not a configuration location
- Read the complete Config Reference
- Copy the full Config Template
- Use the Dragoon Mods Irongoon builder
Option names and enum values are case-sensitive
New campaigns use staged Irongoon settings from their selected SC preset or YAML profile. If no snapshot exists, Irongoon selects a profile, falling back to Legacy config.yaml when no profiles are found, then to Blueprint when no usable configuration is available. Profile selection tries the remembered filename when enabled, default-ig.yaml, then other profiles in filename order, skipping invalid automatic candidates with warnings.
Campaign saves contain a canonical configuration snapshot. Loading an existing campaign applies that snapshot without rereading its source file. To apply an edited file, use Rescan Profiles, select it under Load YAML Profile, then choose Use settings. New campaigns apply it when they start; existing campaigns require saving and reloading. The first load of an older campaign without a snapshot prefers legacy config.yaml for migration, even if newer profile files exist.
Some settings are new-campaign lifecycle settings and cannot be fully applied to an existing save. These include enableAllCharacters and enableAllDragoons. Use Severed Chains' game-state editor when an existing save needs party or inventory correction.
Irongoon contributes a read-only Irongoon (Blueprint) SC preset containing its shipped defaults. Select it and use SC's Add action to create an editable copy. Edit Irongoon settings, choose Use settings, then return to SC's preset editor and confirm its save prompt. Declining that prompt discards the preset draft.
Active Configuration identifies the SC preset; (Modified) remains while the current SC settings or Irongoon draft differ from it, including after Use settings. Loading YAML does not turn that file into the active SC preset. Use settings stages settings without writing YAML. Save YAML Profile, Save YAML As..., and Rename YAML Profile are explicit file operations. Blueprint settings can be used in a campaign without creating a YAML file.
publicSeed is the base for deterministic modes. Given the same Irongoon version, configuration, registered content, and seed, campaign/fixed modes reproduce their assignments.
Modes explicitly named for a battle, transformation, spawn, or per-use randomization can reroll at that lifecycle boundary. Changing installed mods can also change a result when the eligible registry pool changes.
With useRandomSeedOnNewCampaign: TRUE, Irongoon creates and saves a campaign-specific seed when a new campaign starts. With FALSE, campaigns use publicSeed directly.
Yes, but changes intentionally recompute campaign-resolved values when the save is loaded. For example, changing the seed or Dragoon spell unlock mode can change which spell occupies an already-unlocked slot.
Persistent progression such as Addition XP and Addition level remains save data, while transient randomized mappings are rebuilt from the current configuration.
Current Irongoon validates bounds, required effect pools, external tables, registry IDs, and compatible profile data. An explicit invalid profile load fails without changing the current selection or source file. Automatic profile selection can skip invalid candidates with warnings. Unknown YAML keys are ignored with warnings; invalid values for known settings fail validation.
Read the complete exception and correct the named option or source row. For profile changes, load the corrected file and choose Use settings, then save and reload an existing campaign. Common causes include a lower bound above its upper bound, no enabled Addition statuses, or no usable Dragoon spell effect type.
No. Irongoon does not guess that third-party content is structurally compatible.
Another mod can opt in a Dragoon spell through GatherDragoonSpellProfilesEvent or an Addition through GatherAdditionProfilesEvent. Unprofiled custom content remains stock.
The Addition must complete successfully. In addition, an equipped status mask takes priority over the randomized Addition status because Severed Chains currently exposes one physical-attack status source. The Addition status remains suppressed even when the equipment status chance later fails.
No. Current Severed Chains no longer exposes Irongoon's former writable global escape-chance value, so Irongoon parses the settings but does not apply them at runtime. The options remain in the schema for compatibility until a safe per-battle integration exists.
No. Compilation and packaging verify Java and asset integration, but combat, audio, save lifecycle, and randomized runtime behavior still require targeted Severed Chains gameplay checks