Slay the Spire Message Board  

Still getting failed on all the options for the steam version. Have tried all solutions. Thanks for the hard work guys.

Delete trainer and all files in

C:\Users\USERNAMEHERE\AppData\Local\Temp
C:\Users\USERNAMEHERE\Cheathappens\Work

Reboot PC to clear excess memory, get a fresh copy of latest trainer and
make sure trainer in is folder excluded from virus scans.

C:\Users\USERNAMEHERE\Cheathappens

may need to be added to exclusions as well. Run trainer as admin and try again.

Unfortunately even following this, as well as all the other standard CH operations and the advice in the trainer of pausing the game and letting it sit for several moments before attempting again, don't seem to be working.

Even trying to use the cosmos to modify the memory it doesn't seem like the game wants to cooperate. This is using the non beta build, so [Early_Access_013] (01-25-2018) version of the game.

Will need more info on your system, Windows version, anti-virus and any other software that stops processes to boost performance. I would also verify integrity of game files with STEAM.

new trainer posted.

video of it working as of 5 minutes ago:

I don't understand, it still doesn't work for me. I can activate the trainer but it says failed everytime i try an option. Is there something i am missing?

EDIT: Are you guys sure you put in the right EXE? Because when i run the updated trainer from the manager it says in the upper right corner that a new version is avaliable even though i downlaoded the latest.

[Edited by Kimpabooi, 1/27/2018 9:50:14 AM]

Same here, failed on every option and getting the "newest trainer available" message even though i downloaded the latest one already. Shrug. Cheating on this game is kinda pointless anyway since it defeats the entire purpose of playing it. I only downloaded it out of frustration of getting **** RNG last few runs, but with god mode on it would make the game pointless and boring AF. dunno.

I uploaded what was sent. The version ON the trainer says 01-27-2018 so Caliber probably typed in the wrong ID where it checks for an update.