How x753/repo-customcolors works
File structure
• Top level:
• REPO-CustomColors.sln – Visual Studio solution
• REPO-CustomColors/CustomColors.cs, REPO-CustomColors.csproj – the plugin’s source code and project file
• x753_REPO-CustomColors-X.X.X/manifest.json – mod metadata for the mod manager
• x753_REPO-CustomColors-X.X.X/CHANGELOG.md & README.md – release documentation
• No separate “frontend” or “backend” directories: the code compiles into one DLL that runs inside the game process via a mod loader such as BepInEx or r2modman.
README for additional insights
• Purpose: inject sliders into the existing UI
• Deployment: users download the release from Thunderstore and drop the package into their mod folder.
a. Main components
• Game Engine (Unity-based host application)
• Mod Loader (e.g., BepInEx/r2modman)
• CustomColors Plugin Assembly (CustomColors.dll, manifest.json)
• User Interface Controls (RGB sliders)
b. Relationships & interactions
1. At startup the Mod Loader parses manifest.json, loads CustomColors.dll into the game’s process.
c. Architectural patterns & principles
• Plugin architecture: loose coupling to game via event hooks
• Single responsibility: code only alters UI and forwards values
• Declarative metadata: manifest.json drives mod manager integration
d. Key technologies & libraries
• .NET/C# project (msbuild .csproj)
• Unity UI hooking (via reflection or Harmony patches)
• Thunderstore manifest format