2dog 4.7.1.46

2dog

Command-line tool and project templates for 2dog – run Godot as a library from your own .NET entry point. The engine library itself is the 2dog.engine package.

This one package is both a dotnet tool and a dotnet new template package.

New project

dotnet new install 2dog
dotnet new 2dog -n MyGame
cd MyGame

Convert an existing Godot project

One-shot (no install, .NET 10+):

dnx 2dog convert path/to/your/godot/project

Or install the 2dog command globally:

dotnet tool install -g 2dog
2dog convert path/to/your/godot/project

2dog convert

Converts an existing Godot project to 2dog in place – no files are ever moved, renamed or deleted. The Godot project directory becomes the solution root, and host projects are scaffolded as nested subfolders that the Godot editor ignores (each carries a .gdignore):

MyGame/                      <- your existing Godot project (unchanged)
  project.godot
  MyGame.csproj              <- created or minimally patched
  MyGame.slnx                <- created, or an existing .sln is migrated
  TwoDogWebBoot.cs           <- added (web bootstrap, guarded by LIBGODOT_ENABLED)
  MyGame.2dog/   (.gdignore) <- desktop host (your Main entry point)
  MyGame.web/    (.gdignore) <- browser (WebAssembly) host
  MyGame.tests/  (.gdignore) <- xUnit test project

dotnet new 2dog produces the same layout from scratch.

Options:

Using the library directly

This package cannot be referenced from a project (it is a tool package); reference the engine instead:

dotnet add package 2dog.engine