Build multiplayer games.
No C++ required.

Visual classes with a real type system

Schematic is Ferrite's visual scripting system. Create a Schematic Class from Actor, Pawn, Character, First Person Character, Third Person Character or Game Mode, add components, wire a graph, press Play. Graphs compile to bytecode and run inside the engine's VM.

• Gameplay presets. The FPS and TPS parents create Camera, Weapon, Health, Interaction, Input Actions, an Input Mapping and a companion Game Mode for you.
• Checked math and world libraries. Float, integer, vector, rotator, transform and string nodes, line traces, spawn and destroy, health queries and damage events.
• Input Action events. Bind graph events to input actions and mappings edited in the same window.
• Runtime errors with source maps. A divide by zero or an invalid range fails the node with a pointer back to the graph instead of corrupting the world.

using Ferrite.Managed;

[FeClass(SchematicType = true, Schematicable = true)]
public sealed class EngineHum : Actor
{
    AudioSample? clip;
    AudioVoice? voice;

    protected override void OnStart()
    {
        var loaded = World.Audio.TryLoad("audio/engine_hum");
        if (!loaded.Succeeded) return;
        clip = loaded.Value;
        var playing = World.Audio.TryPlay2D(clip, new(Loop: true, Gain: .25f));
        if (playing.Succeeded) voice = playing.Value;
    }

    protected override void OnUpdate(double seconds)
    {
        if (voice is not null) _ = voice.SetPitch(1.1f);
    }

    protected override void OnStop()
    {
        voice?.Dispose();
        clip?.Dispose();
    }
}

C# classes marked Schematicable appear in the Schematic parent picker, so designers can extend programmer-written classes in graphs. Press Build C# Classes in the editor, then Play. Actors, Game Modes, UI widgets, audio and LAN sessions are all reachable from managed code.

Production renderer, production netcode

The SDK ships the production engine runtime as prebuilt binaries. You get the renderer, physics, audio and networking that the engine's own games are built on.

What the install contains

The SDK is built from an explicit allowlist. Every binary is recorded with a SHA-256 receipt, and every third-party notice is included. It contains no engine source, headers, libraries or debug symbols.

Ferrite ships only as this SDK. The engine runtime is prebuilt and closed; all gameplay is written in Schematic or C# against the documented API, and everything a finished game needs is in the box.

Install

# 1. install Ferrite SDK from your Steam library

# 2. run setup once from the install folder
...\steamapps\common\Ferrite SDK\install

# 3. (C# only) install the .NET 10 SDK from Microsoft

# 4. open Ferrite Hub and create a project

Setup registers the Steam install folder as your engine root. Steam keeps the tools, runtime and templates up to date.

Or from the command line

ferrite new MyGame --template CrabBeachFPS --path D:\Projects
ferrite open     D:\Projects\MyGame\MyGame.femproj

# in the editor: edit, press Play, then Package Project.
# output lands in Saved/StagedBuilds/<Platform>/Release/MyGame/
# with the game executable, cooked content and an archive

ferrite package  D:\Projects\MyGame\MyGame.femproj

Packaging is transactional. A failed cook, copy or validation step leaves your previous build untouched.