MainframeEngine 1.1.7

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher. 
dotnet add package MainframeEngine --version 1.1.7
                    


                    

                
NuGet\Install-Package MainframeEngine -Version 1.1.7
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="MainframeEngine" Version="1.1.7" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="MainframeEngine" Version="1.1.7" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="MainframeEngine" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add MainframeEngine --version 1.1.7
                    


                    

                
#r "nuget: MainframeEngine, 1.1.7"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package MainframeEngine@1.1.7
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=MainframeEngine&version=1.1.7
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=MainframeEngine&version=1.1.7
                    


                            Install as a Cake Tool

Mainframe Engine

A modular C# game engine on Vulkan: a Godot-style scene tree with source-generated serialization, PBR materials, cascaded shadows, RmlUi game UI, Jitter2/Box2D physics, SoundFlow audio, multiplayer, gettext localization and Spine animation.

This package is everything a game needs to build and run, with no engine checkout and no editor required:

  • MainframeEngine.dll (and the bundled spine-csharp.dll)
  • the source generator for [Export], [Signal], [Replicated] and [Rpc] members
  • the native libraries for win-x64, linux-x64 and osx-arm64/osx-x64, Valve's steam_api included
  • Steam integration over Facepunch.Steamworks (bundled), which starts when the Steam client runs, Apple Silicon too
  • the engine content (compiled shaders, UI widgets, fonts), which is copied into your app's Assets/ folder
  • build integration: .po → .mo localization, the DEMO define from project.mfproj, and macOS development app bundles
  • player builds: tools/mf-export, the exporter the editor's File › Export runs (see below)
  • surface shaders: tools/mf-shaders and the engine's Slang modules (import mainframe.spatial;), run through the MainframeShaders target (see below)

Requirements: .NET 10, plus a GPU with Vulkan 1.2 (MoltenVK is included on macOS).

Start a game

The quickest way is the mfgame template from the engine repository, or New Project in the optional Mainframe Editor. Both create a game library, a desktop project and project.mfproj that reference this package.

To add the engine to an existing project:

dotnet add package MainframeEngine

using MainframeEngine;

// Reads project.mfproj next to the app (window, input map, autoloads, main scene) and runs it.
return GameHost.Run(args, typeof(MyNode).Assembly);

Copy project.mfproj and your Assets/ to the output folder, as the template's desktop project does.

Surface shaders

Your own shaders are Slang surface shaders: .slang files under Assets/ that start with import mainframe.spatial; (3D meshes) or import mainframe.canvas; (2D items); the engine generates every pass around their vertex() and fragment(). Their SPIR-V is built ahead of time and committed next to them:

dotnet msbuild MyGame.Desktop -t:MainframeShaders                                   # build stale ones (needs slangc)
dotnet msbuild MyGame.Desktop -t:MainframeShaders -p:MainframeShadersCommand=check  # fail on stale ones

slangc comes with the Vulkan SDK or a Slang release. Every build copies the engine's modules to .mainframe/shaders/include for the shader-slang VS Code extension (slang.additionalSearchPaths).

Player builds

Player builds come from export presets in project.mfproj (the editor's File › Export… writes them). The package ships mf-export; MainframeExportTool gives its path:

mf_export="$(dotnet msbuild MyGame.Desktop -getProperty:MainframeExportTool)"
dotnet "$mf_export" --project . --preset "Windows"   # or --all, --list
dotnet "$mf_export" MyGame.Desktop/MyGame.Desktop.csproj osx-arm64 builds   # without a preset (the old package-game form)

It makes <Exe>-<version>-osx-arm64.zip (a signed .app), -win-x64.zip or -linux-x64.tar.gz, with only that platform's natives. macOS presets sign (ad hoc, or a Developer ID) and notarize; they need a Mac.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.1.7 51 11/7/2026
1.1.6 212 10/27/2026
1.1.5 143 10/25/2026
1.1.4 144 10/20/2026
1.1.3 112 10/20/2026
1.1.2 135 10/17/2026
1.1.1 156 10/12/2026