ChroMapper
You need a working ChroMapper installation on your machine. ChroMapper is available at github.com/Caeden117/ChroMapper. The project file references DLLs directly from your ChroMapper installation directory — specifically from theChroMapper_Data\Managed\ subdirectory inside it. If ChroMapper is not installed, the project will not compile.
.NET SDK
Thedotnet new command requires the .NET SDK. Any version that supports .NET Framework 4.8 class library projects and the dotnet new template system will work.
You can verify your installation by running:
The ChroMapperDir environment variable
This is the most important configuration step. The project file and the post-build deploy step both read
ChroMapperDir at build time. If the variable is missing or points to the wrong directory, the build will fail.ChroMapperDir must be set to the full path of your ChroMapper installation directory — the root folder that directly contains the ChroMapper_Data\Managed\ subdirectory.
For example, if your installation is at C:\Program Files\ChroMapper, the directory should contain:
ChroMapperDir to C:\Program Files\ChroMapper — not to the Managed subfolder.
Setting the variable on Windows
Via System Properties (permanent):- Open Start and search for Edit the system environment variables.
- Click Environment Variables.
- Under User variables, click New.
- Set the variable name to
ChroMapperDirand the value to your ChroMapper installation path. - Click OK on all dialogs, then restart any open terminals.
C# IDE (recommended)
The template generates a.csproj file targeting .NET Framework 4.8. You can build from the command line with dotnet build or msbuild, but an IDE gives you IntelliSense against ChroMapper and Unity types.
Recommended options:
- Visual Studio 2022 (Community edition is free) — best MSBuild integration on Windows
- JetBrains Rider — cross-platform, strong Unity support
Quickstart
Install the template and create your first plugin