This is a Verse primer and a reference in one. It doesn't teach programming from zero — it takes the Blueprint nodes you already know (Branch, ForEach, Set, Event Dispatcher, the variables panel) and translates them, one at a time, into the way Verse says the same thing. 9 chapters, 30 lessons, from the name-for-name glossary to a warm-up run at UE6's Scene Graph.
Once you've worked through the whole course, the search above turns this site into a reference manual — worth keeping bookmarked.
Cleared 0 / 30 ★ 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.
Not because Blueprints disappear tomorrow — because you have a window that is exactly the right size.
Unreal Engine 6 merges UE5 and UEFN into a single engine, and its new gameplay framework, Scene Graph, is built from scratch on Verse. Actors and Blueprints are fully supported in UE6 Early Access (targeted for the end of 2027) and the initial releases; deprecation waits until Scene Graph is mature enough. That window is just about long enough to learn the language properly.
Everything you do in Blueprints has a Verse counterpart. The hard part was never the syntax — it's "I know what I want, I just don't know what it's called over there." This course lays both vocabularies side by side so your existing experience carries straight over.
A node graph is a binary asset: you can't paste it to an AI, can't diff it, and a merge conflict means picking one side. Verse is text, which unlocks all of it — and the UE6 editor itself now ships with generative AI assistants built in. Once your logic is words, collaboration changes generation.
9 chapters, 30 lessons, from gentle to deep. All 9 chapters, 30 lessons, plus the reference section are now fully open — no account required. Each lesson ends with a small challenge worth a star ★, and carries 3 extension pages (Advanced / Technique / Deep Dive); explore those after the main quest.
Chapter 1 · Why Verse
Chapter 2 · Blueprint ↔ Verse
Chapter 3 · Data
Chapter 4 · Control Flow
Chapter 5 · Containers
Chapter 6 · Functions & Types
Chapter 7 · Time & Concurrency
Chapter 8 · UE6's New World: Scene Graph
Chapter 9 · Graduation
Appendix · Reference
Nothing to stop for. Epic's public position: Actors and Blueprints are fully supported in UE6 Early Access (targeted for the end of 2027) and the initial releases; deprecation waits until the new Verse-based Scene Graph framework is mature enough, with no date announced — and Epic has committed to shipping conversion tools before anything is retired (not released yet). The real risk isn't "gone tomorrow," it's starting only after the window closes. Lesson 2 lays out the known timeline item by item.
No — but you do need Blueprint experience. This site explains Verse throughout using Branch, ForEach, Delay, Set, Event Dispatchers, and the variables panel, the things you handle every day. Every core lesson carries a "Blueprint Cross-Reference" section that puts both approaches, and their differences, side by side. If you can build in Blueprints, you have all the prerequisites.
You're learning the Verse language, not one editor's menus. That said, the only place you can actually compile and run Verse today is UEFN (Unreal Editor for Fortnite) — Verse has been running in production there for three years — so the examples on this site use it as their runtime. When UE6 arrives, the syntax doesn't change; only the framework it hangs off does (Chapter 8 covers Scene Graph).
You'll be able to translate an existing Blueprint into Verse node by node — exactly what the Lesson 29 graduation project walks through. Along the way you cover variables, conditionals, loops, containers, functions, classes, async and concurrency, and event binding, then move into UE6's entity/component model. The final lesson is about bringing AI into that workflow.
Each core lesson has 3 extension pages attached: "Advanced" explains the theory, "Technique" collects practical approaches, and "Deep Dive" 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.