- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 546
- Reaction score
- 7
Slay the Spire 2 Console Restriction Bypass
Typical dev move: the console is technically present in the build but intentionally gimped. In the current 0.103.0 version, the devs locked it down to exactly four basic commands via a simple IF statement check inside sts2.dll. This patch nukes that restriction, giving you access to the full developer environment that was stripped from public modding sites.
Technical Execution
This isn't a complex memory hack—it's a clean binary patch. By removing the conditional check in the DLL, the engine no longer validates your input against the restricted whitelist, allowing every internal command to fire.
Setup Instructions
Tested and working on the current build. Since it's a local file modification, it's perfect for testing builds or just messing around with game mechanics that are normally hidden.
Anyone found any specific hidden commands for testing relics yet?
Typical dev move: the console is technically present in the build but intentionally gimped. In the current 0.103.0 version, the devs locked it down to exactly four basic commands via a simple IF statement check inside sts2.dll. This patch nukes that restriction, giving you access to the full developer environment that was stripped from public modding sites.
Technical Execution
This isn't a complex memory hack—it's a clean binary patch. By removing the conditional check in the DLL, the engine no longer validates your input against the restricted whitelist, allowing every internal command to fire.
You cant view this link please login.
You cant view this link please login.
Setup Instructions
- Unlock the configuration: Navigate to %APPDATA%\\SlayTheSpire2 and open settings.save with any text editor.
- Add the following line to the file:
Code:
"full_console": true - Apply the binary patch: Go to your game directory at steamapps/common/Slay the Spire 2/data_sts2_windows_x86_64/
- Swap the original sts2.dll with the patched version.
The patch targets the logic flow within the sts2.dll where the console input is parsed. By manipulating the assembly to ignore the command count check, the game engine processes the full dev string. It's recommended to keep a backup of your original DLL in case of a version mismatch after a game update.
Tested and working on the current build. Since it's a local file modification, it's perfect for testing builds or just messing around with game mechanics that are normally hidden.
Anyone found any specific hidden commands for testing relics yet?
