Repository navigation
Troubleshooting
Miooowo edited this page Aug 5, 2026
·
1 revision
NuGet.org may be missing from your package sources:
dotnet nuget add source https://api.nuget.org/v3/index.jsonThen restore / rebuild.
In Rider: File → Settings, search for toolset, and select an MSBuild version that mentions Rider.
Path discovery failed. In Directory.Build.props or local.props, set:
<Sts2Path>C:/Steam/steamapps/common/Slay the Spire 2</Sts2Path>Use your real install path. On Windows the managed data folder is typically data_sts2_windows_x86_64 under that path.
Publish needs MegaDot/Godot. Create Directory.Build.props next to the .csproj and set GodotPath to the .NET / mono executable (not a wrong edition).
- Confirm a
.pckexists under the gamemods/{YourMod}/folder. - Non-code changes require Publish, not only Build.
- Confirm
has_pckistruein{ProjectName}.jsonwhen you ship a pck.
- Keep files under
{ModFolder}/localization/**/*.json. - Do not leave empty JSON files.
- Follow key format
{MODID}_{CATEGORY}_{ORIGINAL_ID}.title/.description. - The stock template includes
engandzhsseeds — restore them if deleted.
- Install the runtime STS2-RitsuLib into
mods(NuGet alone is not enough). - Ensure
{ProjectName}.jsonlists dependencySTS2-RitsuLib. - Match game branch / API: templates target 0.110.1 with package
STS2.RitsuLib. Older branches may needSTS2.RitsuLib.Compat.*packages and matching RitsuLib variant packs. - For auto-registration, ensure your initializer calls RitsuLib discovery / registration (Character template does this; Empty/Content may need the same pattern — see RitsuLib tutorials).
Expected when referencing a platform-specific sts2.dll while building MSIL mods. Templates suppress this warning.
Restore from nuget.org. The templates pin 0.0.1-preview. Update the PackageReference when a newer analyzer is published.
- Setup
- RitsuLib tutorials
- Discord #sts2-modding: https://discord.com/invite/SlayTheSpire