Two build paths — CI stubs or your own game

Two build paths — CI stubs or your own game An architecture diagram generated by Archify. Your clone · .NET 8 SDK · Architecture component Your clone .NET 8 SDK Stub build · -p:GameInterop=refs · Architecture component · what CI does Stub build -p:GameInterop=refs what CI does Gates · dotnet test + standards · Architecture component Gates dotnet test + standards Pull request · CI re-runs the gates · Architecture component Pull request CI re-runs the gates Interop build · BepInEx/interop · Architecture component · or .local/ Interop build BepInEx/interop or .local/ Deploy · install-stellar.sh / copy · Architecture component Deploy install-stellar.sh / copy Your game · Stellar.Framework/ · Architecture component Your game Stellar.Framework/ Logs + captures · DIAGNOSTICS / WIRECAP · Architecture component Logs + captures DIAGNOSTICS / WIRECAP no game then green own client 7 DLLs writes what you saw Legend Frontend Backend Database Security External

No game install

  • • refs/ holds API-only interop stubs
  • • Same build CI runs on every PR

Your own client

  • • Pass -p:GameInterop / -p:BepInExCore
  • • Or drop the interop in .local/ once

Say what you tested

  • • Put the log lines in the PR
  • • STELLAR_DIAGNOSTICS=1 for per-event logs