2dog 4.7.1.59

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.

Run it

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

dnx 2dog             # in a Godot project: add hosts; elsewhere: create one
dnx 2dog new MyGame  # a new Godot project with 2dog hosts

Or install the 2dog command globally:

dotnet tool install -g 2dog
2dog

With no host options the tool prompts: a checkbox list of hosts, editable folder names, the plan, and a confirmation. Naming any host option (or passing --yes) runs it unattended instead. The dotnet new template produces the same output: dotnet new install 2dog && dotnet new 2dog -n MyGame.

What it does

Creates the host projects in place – no file is 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
  MyGame.winforms/ (.gdignore) <- WinForms host (opt-in: --winforms; Windows-only at runtime)

Run it again whenever you want another host – hosts that exist are recognized and left alone, and a kind you already have is added a second time under a free folder name (2dog add --desktop MyGame.editor).

Commands:

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