Realm Works - Where To Begin

Realm Works users often hit the same wall: the interface starts blank, so it’s unclear what to build first. The practical answer offered here is to begin in the Mechanics Reference area—set up the names and items that will be looked up constantly—so the tool’s automatic linking works from the start and reduces table-time searching.

The walkthrough starts by creating a fresh realm (a “Tomb of Horrors” example) and opening it to show an empty workspace: categories, links, homepage, and mechanics reference are all blank. From there, the key demonstration is how automatic link detection turns plain text into connected data. A simple example creates a location (“dirt road”), a person (“Bob”), and an event (“nightly walk”). After saving, Realm Works automatically detects references and creates links between those entities—Bob linked to the dirt road, and the nightly walk linked to Bob and the dirt road. The payoff is long-term: once information is stored in the database with working links, a DM can return months or years later and still navigate relationships without relying on crumpled scrap notes.

A major efficiency point follows: link detection happens at save time, so the strategy is to create the things that will be referenced frequently first. To avoid constant pop-up prompts during linking, the walkthrough recommends enabling auto-accept in Manage Preferences. It also notes how duplicates behave: if multiple entities share the same name, Realm Works prompts for clarification, so using suffixes (like “Bob Jr.”) helps keep references unambiguous.

The workflow is then split into two core zones. The “world” side holds campaign content—places, locations, people, groups, and big events. The “mechanics” side is the database for reusable game elements: monsters, spells, equipment, and tables. The guidance is not to import every rule just because it exists. Instead, only add what will actually be used at the table. If something isn’t referenced after a while, remove it to avoid clutter and unnecessary linking.

To illustrate, the walkthrough describes building a Monster Manual structure inside Mechanics Reference using categories and sub-articles (for example, a “dangerous” category with “monsters” beneath it). The recommended starting step is entering names first—often by pulling the index from the Monster Manual—so links work immediately. Detailed stats can be filled in later during prep for specific modules. The same approach can apply to spells and loot tables, though the walkthrough notes a personal workflow: spell definitions may be maintained in Hero Lab and synchronized with Realm Works, while Realm Works is used mainly for linking spell names.

Finally, the walkthrough addresses overwhelm. Realm Works can request large amounts of information for characters like “Bob,” but a shortcut (Control + Shift + the key next to one) removes empty snippets and sections, leaving only the fields that were actually filled in. The overall message is to start small, build the mechanics that drive linking, then expand the world outward as prep needs grow—because once the data is in the system, it stays available and connected.