Table of Contents

Real Mod Evidence

S1Interop is still alpha. This page tracks what the current test harness is meant to prove against real Schedule One mod projects and where the evidence stops.

The real-mod lanes run against sibling checkouts in the broader local ScheduleOne workspace. They copy projects into temporary folders before applying migrations or build-gate checks, then delete the copies. They should not mutate the original mod repositories.

Evidence Lanes

dotnet run --project .\tests\S1Interop.Tests\S1Interop.Tests.csproj -c Debug -- --integration-backend-neutral
dotnet run --project .\tests\S1Interop.Tests\S1Interop.Tests.csproj -c Debug -- --integration-hoverboard
dotnet run --project .\tests\S1Interop.Tests\S1Interop.Tests.csproj -c Debug -- --integration-build-gates
  • --integration-backend-neutral focuses on generated SDK/facade behavior from real source and reference metadata.
  • --integration-hoverboard is a smaller real-mod loop for Hoverboard SDK generation and migration convergence.
  • --integration-build-gates focuses on sandboxed migration plus Mono/IL2CPP build verification for selected real-mod copies.

Run the full integration lane before release-facing validation:

dotnet run --project .\tests\S1Interop.Tests\S1Interop.Tests.csproj -c Debug -- --integration

Last Local Verifications

On July 5, 2026, the focused backend-neutral real-mod lane passed locally against the current checkout:

dotnet run --project .\tests\S1Interop.Tests\S1Interop.Tests.csproj -c Debug -- --integration-backend-neutral

Result: S1Interop fixture tests passed (9 executed).

The focused Hoverboard lane also passed locally:

dotnet run --project .\tests\S1Interop.Tests\S1Interop.Tests.csproj -c Debug -- --integration-hoverboard

Result: S1Interop fixture tests passed (3 executed).

The focused build-gate lane also passed locally:

dotnet run --project .\tests\S1Interop.Tests\S1Interop.Tests.csproj -c Debug -- --integration-build-gates

Result: S1Interop fixture tests passed (5 executed).

These runs prove the focused backend-neutral, Hoverboard, and selected build-gated coverage listed below against the current local workspace and game reference paths. They are not a substitute for a full release-facing integration pass.

Current Real-Mod Coverage

Mod or fixture Current evidence
S1FuelMod Injected-type analysis, source migration for generated member-access facades, sandboxed migration without mutating source, mono-only copy conversion, and backend-neutral generated facade compilation against both Mono and IL2CPP reference surfaces when local game paths are available.
BarsGraphics Source alias detection, string-held game type discovery, sdkgen --apply, generated facade compilation, and build-gated migration across MonoDevelopment, MonoStable, Il2cppDevelopment, and Il2cppStable style configurations.
Hoverboard Sandboxed migration convergence, sdkgen --apply, namespace-scoped facade generation, owner-qualified generated member aliases for common game member names, and generated SDK compilation against Mono/IL2CPP reference surfaces in focused integration lanes.
bGUI-style dependencies Mixed Mono/IL2CPP configuration inference and staged dependency path handling for bGUI.dll-style references.
S1-VoiceChat Build-gated conversion of a mono-only copy when local dependencies and game paths are available.
BotanistFix Build-gated conversion of a mono-only copy when local dependencies and game paths are available.
BigWillyMod Sandboxed verification for property-based generated-wrapper references.
BetterJukebox Missing runtime define migration and absolute hint-path cleanup.
GunsAlwaysAccurate Baseline clean dual-runtime recognition and SDK namespace detection.
s1-employeetweaks Package-reference runtime evidence and Harmony overload risk reporting.
OTC-S1-Mod Configuration condition evaluation and Harmony transpiler risk reporting.
CasinoDirectDeposit Game-root Mods dependency hint-path migration.
NPCPack Absolute sibling DLL hint-path migration.

IL2CPP Boundary Case Inventory

Recent local scans across the broader ScheduleOne workspace found these recurring IL2CPP-only shapes:

  • BetterJukebox, S1FuelMod, and SteamNetworkLib use Il2CppStructArray<byte> around Steamworks packet reads. These are the real-world basis for the managed byte[] boundary diagnostic and migration analysis.
  • BarsGraphics contains direct object/proxy casts such as pipelineAsset is UniversalRenderPipelineAsset and target is UnityEngine.Object, alongside handwritten TryCast<T>() fallbacks. S1I007 warns on the risky plain-cast shape until migration has a safe object-cast rewrite for all common forms.
  • OTC-S1-Mod and DedicatedServerMod use many TryCast<T>(), Il2CppReferenceArray<T>, Il2CppSystem.Guid, and Il2CppSystem.Collections.Generic.List<T> branches. These are useful references for future general rules around reference-array construction, Guid conversion, and game callback/list signatures.
  • OTC-S1-Mod still has Harmony transpiler usage in at least one IL2CPP-aware project area. The compiler diagnostic intentionally keeps transpilers as hard IL2CPP build errors because there is no safe automatic IL rewrite fallback.
  • Some older demo or generated folders can contain stale migrated output. Treat current temp-copy migration and build-gate results as the source of truth, not old checked-out demo artifacts.

What This Proves

  • The analyzer can read real project shapes, imported props/targets, custom configuration names, package references, and common local path patterns.
  • migrate and verify-migration can run against temporary real-mod copies without changing the original project.
  • Selected mono-only real-mod copies can be migrated far enough for build-gated verification when their unrelated dependencies are available.
  • Backend-neutral SDK generation can be seeded from real source aliases, string-held game type names, and local reference metadata.
  • Generated backend-neutral helper source is compiled against both Mono and IL2CPP reference surfaces in focused cases.
  • Generated Schedule One type facades use the canonical S1Interop.ScheduleOne.* namespace shape and do not emit shortened duplicate S1Interop.* Schedule One facades.

What This Does Not Prove Yet

  • It does not prove that every Mono mod can migrate cleanly in one command.
  • It does not prove runtime behavior for every migrated mod. Runtime smoke coverage exists for backend-neutral demo mods that emit deterministic probe markers, but most real-mod evidence is compile-time and sandbox-verifier evidence.
  • It does not remove the need for human review of Harmony transpilers, arbitrary reflection flows, unsafe delegate surfaces, or mod-specific dependencies.
  • It does not redistribute or vendor Schedule One assemblies, IL2CPP wrappers, or local game files.

Adding New Evidence

For a new real-mod fixture:

  1. Copy the mod to %TEMP%\S1Interop.Tests\<guid> before applying changes.
  2. Pack the current S1Interop.Generators package into a temporary local feed if the fixture exercises generator output.
  3. Use local MonoGamePath and Il2CppGamePath properties for build-gated validation.
  4. Assert that the original project file, source files, local.build.props, and s1interop-runs state were not changed.
  5. Prefer a focused integration lane when the fixture is expensive enough to slow normal iteration.
Edit this page