Unreal Editor for Fortnite: Questions and Answers

Unreal Editor for Fortnite, or UEFN, is Epic's PC tool for building Fortnite islands on Windows. It launched in March 2023. You place devices, write Verse code and test your island in Fortnite. Islands are published through the Creator Portal and follow Epic's Island Creator Rules.

Fortnite Creative 2.0 is a name many creators have used for the PC editor, because it adds Verse code to the device-based building of the in-game creative mode. Epic's own name for the tool is Unreal Editor for Fortnite. Check Epic's documentation for the current wording.

Verse is Epic's programming language for gameplay logic on your island. The code lives in .verse files inside your project. You build it from the Verse menu in Epic's editor and push changes to a live edit session to test them in Fortnite. A device class derives from creative_device.

The timing depends on your island and on Epic's Island Creator Rules, not on SentryEdit. A small island with one button and one item granter is a sensible first project. Publishing happens in the Creator Portal, and you do that step yourself.

Yes. This is the official SentryEdit website, and the download here is the original build. Compare its SHA-256 checksum with the published manifest before you run it. For support, use the Send feedback button inside the SentryEdit app.

No. Generated Verse can contain mistakes, so review every diff and test the result in a live edit session. Ask first pauses before each change, and Plan only changes nothing. The Verse compiler has the last word, and its errors appear in the editor.

Yes. Ask it to write a plain-text notes file in your project folder that lists what changed in each .verse file. With Cron it can refresh the notes on a schedule. Read the file before you share it, because the agent can make mistakes.

Yes, for the Verse side. It can read your code with grep and read_file, list every place the device is used and explain what each call does. Device settings live in Epic's editor, so you check those yourself. Review the diff and test in a live edit session.

Three kinds: a cloud AI provider through a standard API endpoint, a model running locally on your PC, or the built-in model. The Test button checks an endpoint and shows its response time and context window. A cloud AI provider may charge separately.

No, not by itself. SentryEdit runs locally with no telemetry, and chats, project folders and API keys stay on your PC. Prompts go only to the model endpoint you pick. With a model running on your PC, nothing leaves the machine.

A SHA-256 checksum is a fingerprint of a file. Run certutil -hashfile on your download and compare the result with the published manifest. The installer is not code-signed yet, so Windows SmartScreen may warn. Choose Run anyway only after the checksums match.