Verse AI: code that compiles for your Fortnite island

Why general-purpose AI struggles with Verse

Verse is a young language with ideas of its own: failure contexts, effects, suspending functions, modules tied to your project’s folders. An AI assistant that has never seen your project will happily invent an API signature or an identifier, and you find out when you build.

Island Pilot flips that around: the agent works in your real files, checks the API digests in your project and has the editor compile its code. When it introduces an error, it reads it in the diagnostics, fixes it and builds again.

How the Verse Coder writes and builds your Verse code

1. Read. It opens the affected files, starting from the reported file and line, and checks imports, callers and device references.
2. Game state. It works out who owns the data (player, team, round, session, persistence) and reuses the existing source: no second wallet, no duplicate XP table.
3. Write. It fixes the cause, not the symptom. Every write checks the hash of the file it just read, and the change is shown to you for approval.
4. Build. It discovers the Verse schema the editor exposes, then builds with BuildAll when that operation is available.
5. Fix. It reads the returned diagnostics, fixes the errors it introduced and builds again.

If the file changed between the read and the write (because you edited it by hand, say), the write is refused: the agent reads the file again before retrying.

Example requests

• “Add a coin shop to my tycoon and save coins between sessions.”
• “The build fails on line 42 of coin_shop.verse, find the cause.”
• “Give 50 XP to the player who presses this button, once per round.”
• “Wire this device to the door script and check the reference after the build.”

For a bigger request, the orchestrator gives the logic to the Verse Coder and the test checklist to the Tester. A HUD designed in the UI Design tab is built by the UI Engineer, with Verse feeding its values and handling its clicks.

What gets verified, and what doesn’t

A successful build proves the syntax and types are right. It doesn’t prove the gameplay behaves as intended. So the agent’s report keeps these apart:

• the files changed and the cause that was fixed;
• the real build result and its diagnostics;
• the cases to test in game: players joining and leaving, respawn, reset, repeated events.

When the agent finds and verifies a method (a parameter format, a sequence of tools), it can save it as a SKILL.md in your project and reuse it later: see Skills.

What you need

System

Windows 10 or 11 PC (64-bit) with UEFN

Editor

UEFN open on your project, with its MCP turned on

AI

Your own subscription (Claude, ChatGPT, Gemini…), see AI models

Verse knowledge

Not required

Several agents can share the UEFN connection: each one reserves the Verse files it edits until its mission ends, and a build waits for the others to finish their current editor step.

FAQ

Does the AI really compile my Verse code?

Yes, when the editor exposes the operation: the Verse Coder builds with BuildAll through UEFN’s MCP and reads the diagnostics that build returns. It never makes up a result when no build ran.

Can it change a file without my approval?

No. Writing a .verse file checks the hash from the last read and shows you the change to approve. A file that changed in the meantime is read again before any new write.

Will the code work in game?

A build guarantees syntax and types, not in-match behavior. The agent lists what to test in game, and the Tester can prepare a checklist or test files.

Is Island Pilot made by Epic Games?

No. Island Pilot is an independent tool, not affiliated with Epic Games. It works next to UEFN, through the tools the editor exposes. It’s a one-time purchase: see pricing.