Home › 100 Questions › Patches, Beta, Controls & Mods
Current Main and Beta branches, how to switch, the important v0.111.0 changes, controls, Workshop, and mod compatibility.
First principle: Never use a number without a branch and date. In Early Access, the first debugging step is checking whether the player and guide are on the same build.
Short answer
The current tracked lines are Main v0.107.1 and public Beta v0.111.0. Main v0.107.1 includes Major Update #2; Beta v0.111.0 is the experimental branch with the latest balance, interface, localization, performance, and modding changes.
What to do in a run
Read patch notes in branch order: first find your branch, then the card, relic, enemy, or control entry you care about. A beta note is not a Main fact until the change is merged.
Short answer
The current default Steam branch tracked by STS2DB is Main v0.107.1, also called Major Update #2. It is the branch players use when they have not opted into public-beta.
What to do in a run
When a guide says current without a branch, compare its numbers to v0.107.1 first. If the guide only matches v0.111.0, it is Beta advice and may not describe your install.
Short answer
The current optional public-beta tracked by STS2DB is Beta v0.111.0, released August 14, 2026 in the project's version record. It is newer than Main v0.107.1 but is not the default branch.
What to do in a run
Use Steam Properties → Game Versions & Betas to confirm whether you opted in. When testing a Beta change, record the exact patch because the next Beta can revise or revert it before Main receives it.
Short answer
Beta v0.111.0 changes Mirage to cost 1 at both levels, Exhaust at base, and lose Exhaust when upgraded; it reduces Regalite's first-created-card Block trigger from 6 to 4. It also includes broader character balance, localization, UI, multiplayer, performance, and bug fixes.
What to do in a run
The two practical checks are branch and affected card. A Mirage or Regalite recommendation without v0.111.0 or a clear branch label can be numerically wrong even when the strategy idea is sound.
Short answer
In Steam, open Library, right-click Slay the Spire 2, choose Properties, open Game Versions & Betas, and select public-beta. Let Steam finish the branch download before launching.
What to do in a run
Tell friends to use the same branch before starting co-op. Beta is an optional test line, not a permanent replacement for Main, so keep the branch in your bug report and screenshots.
Short answer
Use the same Steam Properties → Game Versions & Betas menu and select None. Steam will download the default Main branch before you launch it again.
What to do in a run
After switching back, re-check the branch and patch number before using a card or relic guide. Do not compare a Beta screenshot with Main and assume an apparent nerf or bug is still present.
Short answer
Main v0.107.1 is the default branch with the larger tested update rolled in. Beta v0.111.0 is an optional experimental branch that can change card text, relic values, controls, multiplayer behavior, and localization before or instead of a Main merge.
What to do in a run
Resolve disagreements in this order: branch, version, checked date, then source. If the exact number matters to a run, use the in-game card text and the matching official patch note as the final authority.
Short answer
The verified version fact is that Beta v0.110.0 introduced a keyboard-only control mode; the exact binding table is version and settings dependent. The current store page still tags the game as Mouse Only, so do not copy an old key map into every branch.
What to do in a run
Open the in-game control settings on the branch you are using and record the displayed bindings. For a reproducible control issue, include whether you are on Main or Beta and whether keyboard-only mode is enabled.
Short answer
The current official store listing tags the game as Mouse Only and does not advertise controller support. Beta keyboard-only mode is a separate feature and should not be described as native controller support.
What to do in a run
Use mouse input on the supported path, or test Beta keyboard-only mode if that solves your setup. If a controller mapper works, describe it as a user workaround and include its device and branch rather than promising universal support.
Short answer
There is no stable official touchpad-specific binding documented in the current sources. Because the store lists Mouse Only, touchpad targeting should be treated as pointer input; if the target cursor is unreliable, use a physical mouse or the Beta keyboard-only mode instead of assuming a hidden game rule.
What to do in a run
When reporting the issue, capture the device, operating system, branch, and the exact card or target that fails. That separates an input-device problem from a card-targeting rule.
Short answer
Yes. Steam Workshop support was added to the default Main branch in Major Update #2 v0.107.1.
What to do in a run
Check the mod's supported game version and branch before subscribing. Workshop availability does not mean every StS1 mod is compatible with StS2, and gameplay-changing mods should match across a co-op party.
Short answer
Yes. Mega Crit says modding is supported and that creating new mods should be easier than porting old ones; Steam Workshop support is on Main v0.107.1.
What to do in a run
Treat mods like versioned software. Read the mod's instructions, keep the same set across co-op players, and disable a gameplay mod before concluding that a card or event behaves differently from the official build.
Short answer
Not easily. The official FAQ says StS2 uses a different engine and a somewhat different architecture, so StS1 mods should not be expected to port without substantial work.
What to do in a run
Look for a dedicated StS2 version or a maintainer's port announcement. A mod with the same name is not proof of compatibility; confirm its Workshop page, branch, and dependency list.
Short answer
Start with the current StS2 modding documentation and the official Discord's modding channels, then build against the branch and game version you intend to support. Mega Crit has said new mod creation should be easier, but StS1 code and assumptions are not a drop-in starting point.
What to do in a run
Keep a tiny first mod: one visible, reversible change with a clear dependency list. Test it on a clean profile, then test co-op only after the single-player build loads and the branch/version is recorded.
Short answer
Major Update #2 v0.107.1 brought four beta patches into Main, replaced The Doormaker with Aeonglass, added the Bestiary and Steam Workshop support, changed the RNG implementation, and included broad balance, multiplayer, art, performance, and bug fixes.
What to do in a run
For a run-specific question, use the official note for the exact card or boss instead of treating the update headline as a complete changelog. The Doormaker replacement is the most important obsolete-guide trap.