Proper .NET tooling is required for a viable scripting workflow.

Currently, development depends on manual map editor steps or a Visual Studio setup that still cannot replace those steps. This creates unnecessary overhead and makes integration with standard tooling difficult.

Publishing the ScriptInterface as a NuGet package goes first. As it only contains abstractions, it should be suitable for open sourcing.

A .NET project template should be provided to enable reproducible builds and eliminate setup friction. The template should include a ready-to-use scripting environment.

Additionally, a dedicated .NET CLI tool should replicate the map editor’s manual operations, enabling a complete workflow outside the editor.

This tool should support compiling scripts (matching editor behavior), automated testing (e.g. launching the game with the script enabled, potentially via CLI arguments), and packaging (producing a valid script file or extension, similar to ScriptLinker).