Verse Wiki — the interactive handbook for Verse developers

Hello, developer

This is a Verse learning site: interactive tutorials for the Unreal Engine and UEFN ecosystem. 7 chapters, 23 lessons — from your very first line of code to a graduation project, and every example runs right in the page.This is a Verse learning site: interactive tutorials for the Unreal Engine and UEFN ecosystem. 7 chapters, 23 lessons, built to pave the way for Blueprint creators — starting from the node-based thinking you already know and ending with working code you wrote yourself.

Start Lesson 1 → Browse lessons
My progress

Cleared 0 / 23 ★ x 0

Your progress and stars live in this browser. Acing a quiz, filling in a blank, or hitting "Finish this lesson" all get recorded.

Why learn Verse?

Fair question first: what is it actually good for? Verse has an unusually confident answer.

Built for the Unreal ecosystem

Verse is becoming an increasingly important programming language across the Unreal Engine and UEFN ecosystem. Learn it properly now, and every line you write will pay off in your future development workflow.

Hard to crash

A Verse conditional doesn't ask "true or false?" — it asks "can this succeed?" If it fails, it's skipped and the game keeps running. Classic crashes like null references and out-of-bounds array access often can't even be written.

A Verse conditional doesn't ask "true or false?" — it asks "can this wire go through?" If it can't, it's skipped and the game keeps running. Your old Blueprint friend Accessed None and its crash-cousins? Many of them simply can't be written here.

From player to creator

Unreal Engine and UEFN are pulling "playing games" and "making games" ever closer together. Speak their language, and you're already riding the wave.

Course Map

7 chapters, 23 lessons, from gentle to deep. Clear them in order — each lesson ends with a small challenge worth a star ★. Core lessons also come with deep-dive and tricks extension pages; explore those after finishing the main quest.

Chapter 1 · Getting Started

  1. 01Meet Verse and UE6
  2. 02Your First Device: creative_device
  3. 03Comments, Modules, and using

Chapter 2 · Data

  1. 04Constants and Variables
  2. 05Numbers: int and float
  3. 06string and String Interpolation
  4. 07logic and enum

Chapter 3 · Control Flow

  1. 08if and Failure Contexts
  2. 09Operators, the Full Tour
  3. 10Looping with for
  4. 11loop, break, and defer

Chapter 4 · Containers

  1. 12Arrays: array
  2. 13Maps: map
  3. 14option and tuple

Chapter 5 · Functions & Classes

  1. 15Functions and Implicit Return
  2. 16class and Inheritance
  3. 17struct and interface
  4. 18Specifiers and Attributes

Chapter 6 · Async & Devices

  1. 19suspends and the Flow of Time
  2. 20Concurrency: spawn / race / sync
  3. 21Devices, @editable, and Events
  4. 22Persistence with <persistable>

Chapter 7 · Graduation

  1. 23Graduation Project: Button Opens the Door

Appendix · Reference

  1. ◇Glossary
  2. ▢Syntax Cheatsheet

FAQ

Do I need programming experience?

Not at all — and this site teaches everything two ways, switchable any time from the top-left corner: Blueprint mode explains Verse through Branch, ForEach, Delay, and Event Dispatchers — the things you handle every day in Blueprints; C++ mode is for people who have written code before and compares language features head-on. Every new concept comes with a game metaphor and a little experiment you can poke at yourself. If you've played Creative mode, you already have all the prerequisites.

How does Verse relate to Unreal Engine and UEFN? Where can I run it?

Verse is the programming language Epic built for the Unreal Engine and UEFN ecosystem, and it keeps evolving along with that ecosystem. The most direct way to run Verse right now is to install UEFN (Unreal Editor for Fortnite), the creation environment inside Fortnite — every example on this site runs there.

What will I be able to do after the 23 lessons?

You'll be able to read and write device logic yourself: variables, conditionals, loops, functions, and event binding all get covered, and at the end you build a complete mechanism like "button opens the door" — press the button, the barrier vanishes, and it restores itself a few seconds later. That "event-driven devices working together" pattern is the backbone of Verse development.

What are the extension pages? Do I have to read them?

Each core lesson has 2-3 extension pages attached: "Deep Dive" explains the theory (like the transactional model behind rollback), "Tricks" collects clever techniques from the community (with sources credited), and "Extras" fills in surrounding knowledge. They don't count toward completion, and skipping them won't hurt the main quest at all — but come back to them after finishing the main line and you'll find a second layer of "so that's how it works" fun.

How was this site built?

Pure vanilla HTML / CSS / JS: zero frameworks, zero build step, and pages load no external resources at runtime (even the fonts are self-hosted). The syntax highlighting, the interactive engine, and the pulsar waveform are all small hand-written scripts. Once you sign in, your progress and your Blueprint / C++ mode preference sync to your account and follow you across devices.