Verse Coder: the Verse AI that codes your Fortnite gameplay

A Verse AI for Fortnite, inside your project

Verse is the programming language of UEFN (Unreal Editor for Fortnite). The Verse Coder uses it for your island’s gameplay: device events, multiplayer state, data models, currency, progression and persistence. It writes new .verse files within your project’s existing structure, refactors existing ones and diagnoses compile errors.

Before adding anything, it works out who owns the state: the player, the team, the round, the session or the save. It keeps one source of truth for currency and progression instead of creating a second wallet or XP table, and reuses your project’s modules before designing new ones.

How it works

1. Read: it opens the affected files and the real compiler diagnostics, starting from the reported file and line. It checks imports, signatures, callers and device references.
2. Fix: it addresses the root cause, checking failure contexts, effects, suspension, repeated events and subscription cleanup.
3. Write: every write checks the hash from the last read and shows you the change to approve.
4. Build: when the editor’s MCP exposes BuildAll, it builds, reads the diagnostics, fixes what it introduced and builds again.

It relies on the uefn-verse-devices Skill and its references: API lookup, effects and failure, concurrency. When it verifies a method, it can save it as a learned skill in your project and reuse it later (see Skills).

It works on its own when you talk to it directly, or on a task from the orchestrator. In-game UI belongs to the UI Engineer, which wires its widgets to the same game state, NPC behavior to the NPC Author and checks to the Tester.

Example prompts

• Add a coin shop to my tycoon and keep coins between sessions.
• round_manager.verse stopped compiling after my last change: find out why.
• Give 50 XP to the player who captures the zone, once per round.
• Reset every player’s upgrades when a new match starts.
• Wire the counter button to the purchase logic without duplicating player balances.

Tools and connections

Files

reads and writes .verse files in the allowed project folder

Build

BuildAll through UEFN’s MCP, when the editor exposes it

Connection

UEFN

Starting Skill

uefn-verse-devices

Works with

Orchestrator, UI Engineer, NPC Author, Tester, Reviewer

Limits

A successful build proves syntax and types, not gameplay. The Verse Coder tests join and leave, respawn, reset and duplicate events only when it can reach a live session; otherwise it finishes the file work and names the exact check that is still open. Without an open editor or BuildAll in the catalogue it cannot build, and it never hides an error behind a placeholder implementation.

For the full picture of code in Island Pilot, see Verse code, or go straight to pricing.

FAQ

Do I need to know Verse?

No. Describe the behavior you want in plain words and it writes the code. Every change is shown to you before it is applied, so you can also learn by reading.

Does the code it writes actually compile?

It builds through the editor when UEFN exposes BuildAll, reads the returned diagnostics and fixes the errors it introduced. It never reports a build that did not run.

Can it change my existing code without breaking things?

It reads files and their callers before writing, makes the smallest complete change and refuses to write a file that changed since it was read. You stay in control of every change.

Can I change its AI model?

Yes. Its profile is customizable: provider, model, reasoning effort, Skills and permissions. See AI models.