Zum Inhalt springen

Slay the Spire mods: ModTheSpire, BaseMod and StSLib explained

Official image from Slay the Spire
Image: official, via Steam.
Von ModsDrop Veröffentlicht am 9 November 2026 · 3 Min. Lesezeit

This guide is for Slay the Spire players who want to add community mods without breaking their install. By the end you will know how to get ModTheSpire, BaseMod and StSLib running through the Steam Workshop, and how to set them up by hand if you prefer not to use the Workshop.

Back up your save before you add anything. Mods can change how runs behave, and it is easier to recover a clean save than to untangle a modded one later.

What each tool actually does

ModTheSpire is the loader. It lets mods run alongside the base game without editing the original game files, which keeps your install clean and makes mods easy to turn off later.

BaseMod adds a modding API and a developer console that other mods build on. Many mods list it as a requirement because it handles things a single mod cannot do on its own.

StSLib is a shared library. A good number of mods depend on it for shared code, but not every mod needs it, so only add it if something you have subscribed to asks for it.

Installing through the Steam Workshop

This is the simpler route for most players, since Steam handles the downloading and keeps files in the right place.

  1. Open the Slay the Spire Steam Workshop page and subscribe to ModTheSpire, BaseMod and StSLib.
  2. Subscribe to any other mods you want to use.
  3. Wait for Steam to finish downloading everything before you launch the game. Large mod lists can take a moment.
  4. From your Steam library, select Slay the Spire and press Play, then choose “Play with Mods” rather than the normal launch option.
  5. In the ModTheSpire window that opens, tick the boxes for the mods you want active this session, including BaseMod and StSLib where required.
  6. Press Play inside that window to start the modded game.

A desktop shortcut will launch the unmodded game, since it skips the ModTheSpire step entirely. Always launch through Steam and choose “Play with Mods” when you want mods active.

Manual install without the Workshop

If you are installing files by hand instead of through the Workshop, the layout is straightforward.

On Windows and Linux, put ModTheSpire.jar in the same folder as desktop-1.0.jar, which is your game install folder. Create a mods folder next to it, if one does not already exist, and place mod files inside that folder. Start the game using MTS.cmd on Windows or MTS.sh on Linux, since these scripts launch ModTheSpire using the Java 8 version that ships with the game rather than whatever Java you may have installed separately.

On Mac, the same files go inside SlayTheSpire.app/Contents/Resources rather than a separate install folder. The structure is the same once you are inside that folder: ModTheSpire.jar alongside the game jar, and a mods folder for the mod files themselves.

Picking mods each session

You do not have to run every mod you own every time. The ModTheSpire window lets you tick only the mods you want for that session, so you can test one mod on its own or combine several once you know they work together.

If a mod needs BaseMod or StSLib, tick those alongside it. Leaving a required library unticked will stop that mod from loading correctly.

If something goes wrong

If the game will not start with mods active, try unticking everything except ModTheSpire, BaseMod and StSLib, then add mods back one at a time to find the one causing trouble.

If you installed manually and nothing loads, check that ModTheSpire.jar sits next to desktop-1.0.jar (or inside the Mac Resources folder) and that your mods folder is in the correct location beside it.

To undo any of this, untick mods in the ModTheSpire window to disable them for a session, or unsubscribe on the Workshop to remove them entirely. For a manual install, deleting the mod files from the mods folder removes them, and deleting ModTheSpire.jar returns the game to its unmodified launch.

One thing to remember for later

These tools are built for the original Slay the Spire. If you move on to Slay the Spire 2, it has its own separate mod setup, and none of ModTheSpire, BaseMod or StSLib carry across to it.

Keep a short note of which mods you have active for a run you care about, since reproducing an unusual seed or build later is far easier when you know exactly what was ticked in ModTheSpire at the time.

← Alle News