Rules edition: This is cross-edition Dungeon Master guidance for D&D. Map scale, exploration prompts, and story hooks below are planning suggestions, not new rules. If you use a named spell, monster, class feature, or travel procedure, identify the 2014 or revised 2024 source and use that text consistently. A hex on a map is not the same thing as a magical curse or the hex spell.
Hex maps and curses can both make a campaign feel uncertain: one asks what lies beyond the next landmark, while the other asks what a character or community will do about a supernatural problem. They work best when they create choices rather than extra bookkeeping. Decide what you want players to wonder about, then add only enough structure to support that question.
Use “hex” precisely
At the table, “hex” may mean a hexagonal map space, a curse described in the fiction, or a spell called hex. These terms do not share one set of mechanics. The spell has rules text in the selected rules source; a map grid is a way to represent space; and a story curse may be entirely narrative unless the DM gives it explicit effects. Before a session, name which meaning you intend so players do not mistake a story description for a rules condition.
Choose a useful map scale
Pick a distance for each hex that fits the campaign’s geography and travel pace. A small regional map can make individual landmarks and detours matter; a larger scale can summarize a journey across a broad frontier. No single hex size or percentage of occupied spaces is required here. Treat scale and map density as preparation choices, and tell the players what their characters can reasonably learn about distance and terrain.
Give each region a few memorable features: a settlement, a dangerous crossing, a resource, a rumor, or a visible landmark. Leave some spaces quiet. An empty stretch can make a later discovery feel earned and gives the party room to choose its route. Prepare what changes when the characters spend time, make noise, or follow a clue, rather than filling every hex with a combat encounter.
Set travel expectations with the exploration procedures in the Dungeon Master’s Guide version your group uses. Terrain, weather, mounts, character features, and the group’s pace can all matter; do not apply one blanket speed penalty to every winter journey. If you want a harsher travel challenge, explain the relevant procedure before it becomes a high-stakes surprise.
Make encounters support exploration
Choose an encounter cadence that fits the intended tone, then use the same approach consistently. You might check at a day’s end, after a noisy event, or when a route crosses a particularly dangerous area; those are DM procedures to select, not a universal rule to roll for every hex. A small table can include danger, opportunity, evidence, and quiet results so exploration does not reduce to repeated combat.
Make discoveries actionable. A traveler may know a safer ford, a strange track may point toward a nearby lair, or a weather change may force the group to decide whether to press on or shelter. Give players enough information to choose among routes, and let their map notes matter later. If a group prefers less inventory tracking, focus instead on time, relationships, and the consequences of their choices.
Build a curse around its story purpose
First decide what the curse is meant to do in the adventure. It might reveal a past wrong, create a dilemma, threaten a location, or give an antagonist leverage. A curse can remain a narrative problem; it does not need to add a new penalty or condition. If you introduce mechanical effects, write them down and make clear who is affected, when the effect begins, how long it lasts, and what can end or resist it.
Tell players what their characters can notice before an effect becomes irreversible. Clues may point to the curse’s source, its pattern, or the kind of help that could answer it. This gives the party meaningful investigative choices without promising that every curse has the same solution. A ritual, bargain, destroyed object, or spell might fit a particular story, but do not present one of these as a universal D&D rule unless the chosen source says so.
If the curse escalates, agree on the stages before play and signal changes through the fiction. Escalation should create a decision or lead, not quietly remove a player’s control of their character. Ask about boundaries when the subject matter includes coercion, illness, body horror, or harm to a character’s community.
Review homebrew curse abilities carefully
When a player proposes a curse-themed subclass or feature, start with the complete text and its intended class edition. The word “hex” does not establish a feature’s range, action cost, target, saving throw, or duration. Check those details against the source the character uses, then consider how the full effect interacts with attacks, spells, Concentration, conditions, and the rest of the party.
Playtest against a specific question: Does the feature create an interesting target choice? Does the affected creature have a way to respond? Does the feature crowd out other choices or remain useful in every encounter? Compare it with published options from the same class framework, change one part at a time, and record the version tested. A damage total alone cannot show whether a control or support feature is fair.
For a character-facing design process, see the Oath of Hexes homebrew concept and design guide. For the separate DM approval checklist, see how to evaluate an Oath of Hexes document for a campaign.
Official Rules Sources and DM References
- 2014 Dungeon Master’s Guide: campaign creation, wilderness, exploration, and encounter guidance.
- 2024 Dungeon Master’s Guide: use the revised book’s own procedures when the campaign follows those rules.
- 2014 Basic Rules: spell descriptions.
- 2024 Basic Rules: spell descriptions.
- D&D Beyond: hex spell entry; check which rules version is selected.
