Skip to content
Anomaly

Build Caveats and External Dependency Notes

Intended scope

Section titled “Intended scope”
  • Hard-coded HintPath entries in Anomaly.Client.csproj — which ones, why they exist, how to point them at a local SCP:SL install for development.
  • Per-project TargetFramework quirks:
    • Anomaly.Client.Api — net6.0, IL2CPP.
    • Anomaly.Server / Anomaly.Shared — .NET Framework 4.8 (LabAPI constraint).
    • Anomaly.Launcher — net8.0, Avalonia, single-file publish.
    • Anomaly.Installer / Anomaly.InstallerCore — net6.0, single-file publish.
  • Legacy MSBuild quirks called out in AGENTS.md.
  • Deploy layout — which DLLs land in Mods/, which in UserLibs/, which in the LabAPI plugins/ folder.
  • Signing / strong-naming — not currently used; note where that would need to change if introduced.

Sources

Section titled “Sources”
  • E:\Projects\AnomalyLabs\Anomaly\AGENTS.md — the dev-guide file for internal build conventions.
  • Each project’s .csproj — TargetFramework, HintPaths, publish settings.