Mothmade Gamesdrawn to strange lights

The engine we make our games on

November Engine

A game engine built for real artists using AI coding tools.

Availability

We are planning to release the engine under a permissive license when we are ready to support other developers, but at this time we are not able to do that.

01

Agents it works with

Any agent, one bridge

The editor speaks MCP and has a CLI. Any coding agent that can interact with MCP or a CLI can use the engine — though we consider MCP the golden path, as our deeper integrations there are built for coding agents, while the CLI path is made for people. Nothing in this bridge or in the November skill library is specific to any coding agent, but Claude Code is the one we use every day.

Claude Code

02

How it plugs in

The bridge

The bridge talks to the engine over whatever endpoint the session needs: a Unix socket, a named pipe on Windows, or a TCP socket when the agent is not on the same machine. The server is not an editor feature — it runs inside any November executable. The editor simply extends it with editor tools, which is also how we debug the editor itself.

Assets, resources, skills

Hand-written skill files teach the agent how to use the editor, and document how to author each resource type. Resources are the runtime versions of your assets. Assets are your files from Blender, Photoshop, Autodesk, or any of dozens of other applications. The goal is to let you use the tools you already know, and not have to worry about how "getting it into the game" actually works. We strive to be able to load whatever you are working with.

agent
Claude Code
Pi
OpenCode
GitHub Copilot
stdio
json-rpc
november_mcp.py
one bridge process per agent
finds the editor by endpoint file
unix socket · pipe · tcp
November Process
control server
data model · schemas
views · build (when communicating with editor)
03

Features

Remote access

Point the server at TCP and the agent can be run on your laptop, while the actual engine runs on another box entirely. So if you're debugging a teammate's build, or even something running on a dev kit, you can still use your agentic coding tools.

Because the server runs in the November engine itself, you can debug your game through the same tunnel you use to reach the editor.

When we get our wings on console dev kits, we plan to make this work there too.

Tablet-first navigation

Our editor integrates with your Wacom tablet directly, and all of our tools work as though you are drawing directly on the world. The editor uses your game's own shaders, so the editor feels like you are drawing the world of your game right there in the actual game world, without jumping back to another application.

In-world agents

Agents can be created in the world, visually. Point at a space, a room, an entity, or nothing in particular to place an agent there — the session persists across editor restarts, so you can keep your agents arranged sanely in the game world. Because the agents receive the context in which they were invoked, clicking a light and saying "Turn this on" works, without you needing to clarify what light you mean.

wanted: an in-world agent chat opened against a prop in the scene view
04

Pipeline

Resources

Resources are defined by JSON or YAML files, with JSON schemas generated via our C++ reflection library.

The schema defines the contract for coding agents to generate the resource files for you, which saves you the busywork of getting your artwork into the game.

Scripting

Gameplay code is written in Python, running without the GIL, not on the render thread. The engine is bound to Python via a reflection bridge, built on our own C++ reflection system.

A new engine type shows up in script — and in the schemas an agent reads — without a line of hand-written binding code.

Interface

We use HTML for all of our UI, including the editor, through Ultralight. This lets games draw full web pages into textures, which we can show as a menu or even inside a scene.

05

Where the tools stop

Built for this

The engine was designed around the idea that agents write the code, and an artist, or even the user, generates the actual art of the world. Our goal is to let the AI help you put your own artistic expression into the game. The tools don't design the game — you do.

What the AI does

Game logic (always with human review), custom editor tooling, rigging, motion capture.

never

Dialogue, art, music, puzzle and level design.

06

Questions

Does an agent drive the editor by clicking?

No, but it can still click around to help a moth find their way to the "Add Lamp" button.

Can I license or download the engine?

Eventually, yes. We currently do not have the resources to support other teams working in our engine, so we are not distributing the source code at this time. We hope to eventually release the engine source code under a permissive license, for everyone to use.

Can I download the code at least?

Maybe. Email us at info@mothma.de.