ModTheSpire patched today because The Watcher came out of Beta and I had to disable all my charater mods to play until they update to the new MTS

Originally posted by JoeyArmageddon:

ModTheSpire patched today because The Watcher came out of Beta and I had to disable all my charater mods to play until they update to the new MTS

Oh really I had no idea do you have any idea when ModTheSpire is going to get update so it will work again??

I have the same trouble today,
I don't know if it can change back.

It's not MtS that needs to be updated (it already has been), it's the characters themselves. The Servant (which is the example you're using) hasn't been updated in over a year now, so ofc it won't work with 2.0 just yet.

Originally posted by arek75:

It's not MtS that needs to be updated (it already has been), it's the characters themselves. The Servant (which is the example you're using) hasn't been updated in over a year now, so ofc it won't work with 2.0 just yet.

If that's so do you know if SlaytheSpire allows you to move back before the update because I'd rather play these mods then the new characters.?

Yep, you can do it in Slay the Spire's properties - under Betas, you can choose to go back to versions 1.0 and 1.1 (for almost all of the mods you want to play that aren't 2.0 compatible, 1.1 is what you want).

Now...something I did for myself - I copied the Slay the Spire folder (set to 1.1 when 2.0 was still a beta) to another folder in SteamApps/Common (called it OldStS, I think). I then downloaded ModTheSpire from its github page, copied MTS.cmd (only) into the OldStS folder, and then edited it (MTS.cmd) to load mts-launcher.jar instead of ModTheSpire.jar. This somehow sets the classpath correctly so that mods get loaded directly from the Steam Workshop, which in turn lets them be updated by Steam if and when the authors get around to it.

--Arek75

P.S. There's been another patch-update to StS, which re-enables a couple of methods that were heavily used by 1.1 character mods (getColor and ExhaustAction). Since those have been re-enabled on 2.0, you might try loading these character mods again and seeing if they work, tho iiuc The Servant still crashes with certain of her cards.

Originally posted by arek75:

Yep, you can do it in Slay the Spire's properties - under Betas, you can choose to go back to versions 1.0 and 1.1 (for almost all of the mods you want to play that aren't 2.0 compatible, 1.1 is what you want).

Now...something I did for myself - I copied the Slay the Spire folder (set to 1.1 when 2.0 was still a beta) to another folder in SteamApps/Common (called it OldStS, I think). I then downloaded ModTheSpire from its github page, copied MTS.cmd (only) into the OldStS folder, and then edited it (MTS.cmd) to load mts-launcher.jar instead of ModTheSpire.jar. This somehow sets the classpath correctly so that mods get loaded directly from the Steam Workshop, which in turn lets them be updated by Steam if and when the authors get around to it.

--Arek75

P.S. There's been another patch-update to StS, which re-enables a couple of methods that were heavily used by 1.1 character mods (getColor and ExhaustAction). Since those have been re-enabled on 2.0, you might try loading these character mods again and seeing if they work, tho iiuc The Servant still crashes with certain of her cards.

Thanks for the help but I tried using 1.1 and 1.0 but it still wouldn't work for some reason so I think I'm just going to remove SlaytheSpire, I'm not going to waste my time if I can't use the mods.

Originally posted by xGambitxX:

Thanks for the help but I tried using 1.1 and 1.0 but it still wouldn't work for some reason so I think I'm just going to remove SlaytheSpire, I'm not going to waste my time if I can't use the mods.

Before you do that, I just did the work to get The Servant working with 2.0. The PR is up on GitHub, and I'm about to post a comment on the mod's workshop about it. Here's hoping BlackRuse pushes the update fairly quick. :)

--Arek75

P.S. What other mods are you having trouble with?