The digest Files: An API Dictionary Fresher Than the Docs Site

1. What the digest Is: Four Dictionaries, Delivered with Every Build

Every time you build Verse code in UEFN, the project generates a set of files ending in .digest.verse. They are machine-generated API inventories: the complete signature of every Verse API available in your current environment — every module, every class, every function — listed verbatim, comments included, as a document in Verse source format.the full shape of every Verse API you can use in your current setup — every module, every Blueprint class, every function — meaning its "signature" (what input pins it takes, what it returns), laid out verbatim in one document along with its description. Four dictionaries, each covering its own turf:

Notice anything? The dictionaries split into volumes exactly along the three domain-style paths from Lesson 3 — the digest is organized by module path, so the moment you find an API you also see which module it belongs to, and you instantly know which using line to add at the top of your file. The two lessons dovetail perfectly.

2. Why It's Fresher Than the Website

The web API docs are written and published by humans, so they're always half a step behind; the digest is generated at build time straight from the version installed on your machine, in strict sync with the UEFN in your hands. That makes a practical difference: when new devices or functions ship, the digest often already carries the full signatures while the web docs haven't been written yet. So when a veteran hits an API the site can't find, the first move isn't refreshing the page — it's opening the digest and searching.

The other win is accuracy: the digest is machine-generated, so signatures can't be copied down wrong; and it only lists the APIs that actually exist in your current version — it will never teach you a long-removed function the way an old tutorial might. Lesson 3's advice to check uncertain APIs against the Verse API Reference usually lands, in practice, as "check the digest".

3. How to Use It: Ctrl+Click, Straight to the Definition

The smoothest entry point is VS Code: hold Ctrl and click any class or function name in your code (say, creative_device), and the editor jumps straight to its definition inside the digest — signature, doc comment, and home module all on one screen. You can also open a digest file and full-text search it — hunting for "everything button-related"? One search beats paging through the website by a mile.

using { /Fortnite.com/Devices }

# Hold Ctrl and click creative_device below —
# it jumps straight to its definition in Fortnite.digest.verse
probe_device := class(creative_device):

    OnBegin<override>()<suspends>:void =
        Print("Go take a stroll through the digest")

(Reading the graph: this is the plainest device imaginable — parent class creative_device, one Print String inside Event BeginPlay; the point isn't the code, it's parking your cursor on creative_device, holding Ctrl, and clicking — straight into the dictionary to see its full definition.)

Two things to keep in mind: first, the digest is a build artifact — hand edits do nothing, the next build regenerates it, so don't expect to patch new features into it; second, it's read-only reference material, not a module for you to using — imports still go through the normal paths. Make "unknown API? open the digest first" a piece of muscle memory, and your lookup speed will lap the classmates who only know how to search the web.

Sources & Further Reading

Compiled from community tutorials and official documentation:

• Romero Blueprints: UEFN Verse and Fortnite.digest ↗
• Epic official docs: Asset Reflection and Assets.digest ↗