The Alexandrian


June 1st, 2012

Hexcrawl Map

As part of my essay on game structures in roleplaying games, I specifically discussed the basic structure of the hexcrawl:

(1)   Draw a hexmap. In general, the terrain of each hex is given as a visual reference and the hex is numbered (either directly or by a gridded cross-reference). Additional features like settlements, dungeons, rivers, roads, and polities are also typically shown on the map.

(2)   Key the hexmap. Using the numbered references, key each hex with an encounter or location. (It is not necessary to key all of the hexes on the map.)

(3)   Use (or design) mechanics which will let you determine how far the PCs can move while traveling overland. Determine the hex the PCs start in and track their movement.

(4)   Whenever the PCs enter a new hex, the GM tells them the terrain type of the hex and triggers the encounter or location keyed to that hex: The PCs experience the event, encounter the monsters, or see the location.

Initially a core component of roleplaying games, the hexcrawl structure slowly faded away. By 1989 there were only a few vestigial hex maps cropping up in products and none of them were actually designed for hexcrawl play. 2nd Edition removed hexcrawling procedures from the rulebooks entirely. It wasn’t until Necromancer Games brought the Wilderlands back into print and Ben Robbins’ West Marches campaign went viral that people started to rediscover the lost art of the hexcrawl.

During my discussion of game structures,  I mentioned that I had been developing and playtesting a robust structure for hexcrawling. Since then I’ve received several requests to share my rules for hexcrawling. Although still very much a work in progress, over the next few days I intend to do exactly that.


Before we get to the actual hexcrawling, however, I want to take a moment to clarify what my design goals were (and are) for this project.

First, I wanted a structure which would hide the hexes from the players. Although I find the abstraction of the hex extremely convenient on the GM’s side of the screen (for tracking navigation, keying encounters, and so forth), I’m of the opinion that it has negative effects on the other side of the screen: I want the players interacting with the game world, not the abstraction. Therefore, the hexes in this hexcrawl system are a player-unknown structure.

Second, building on that, the structure is explicitly designed for exploration. The structure, therefore, includes a lot of rules for navigation, getting lost, and finding your way again. It’s built around having the players constantly making new discoveries (even in places they’ve been before).

Third, the system is built around the assumption that every hex on the map will have at least one keyed location. And note that I said “location”, not encounter. Traditional hexcrawls will often included hexes keyed with encounters like this one (from the Wilderlands of Magic Realm):

A charismatic musician sits on a rock entertaining a group of Halfling children. He sings songs of high adventure and fighting Orcs.

While this system certainly could be used with such keys, my intention was to focus the key on content that could be used more than once as PCs visit and re-visit the same areas. (Particularly useful for an open gaming table.) In other words, the key is geography, not ephemera.

Fourth, to support all of these goals (hidden hexes, exploration, reusable material) I wanted to introduce uncertainty into whether or not the keyed content of a particular hex would be experienced (instead of automatically triggering the content when the hex was entered). Furthermore, I wanted a rich system for generating encounters (in order to both create content and to replace the ephemeral hex keys I had eschewed). I accomplished both of these goals by creating a unified, streamlined system of encounter checks.

Go to Part 2: Wilderness Travel

7 Responses to “Hexcrawl”

  1. Monstah says:

    I found your site this week, and found many, many pearls here. Today again, this is a most happy find: in my next session, two weeks from now, I’ll probably run out of excuses to keep my players trapped in a Son of Ether building, and they’ll reach the part of the quest in which they explore the Umbra.

    Great finding, great timing. Thank you!

  2. Jack says:

    I’m currently running a semi-open table-like hexcrawl game (tonight I get to be a player rather than the dm!). I’ve cobbled together a rough collection of mechanics for encountyers and getting lost and foraging for food. there are A LOT of tables involved, and even at that I feel like the content is really limited (my random tables have encounter seeds that I can/have to build details up around, but it’s only 20-30 seeds per terrain type). I’m really interested to see what sort of system you’re using and see what I can use to improve mine.

  3. Ed says:

    I don’t know if you have seen it or not, but I remember Paizo made an adventure path called Kingmaker which has several aspects for exploring a Hexmap. Perhaps you can find some cool ideas from there to mine. Wish you luck in your endeavors!

  4. Yahzi says:

    Looking forward to more of this!

  5. The Alexandrian » Hexcrawl | El trastero de Padre, Marido y Friki says:

    [...] The Alexandrian » Hexcrawl [...]

  6. Hexcrawl Resources | ars phantasia says:

    [...] Hexcrawl: a very useful series of posts by Justin Alexander on his philosophy behind designing the mechanics of a Hexcrawl. [...]

  7. Two Ways to Design Hex Encounters | ars phantasia says:

    [...] for doing so.  Justin Alexander is one of them.  Allow me to quote at length a couple of the design goals which led him to introduce a system quite different from that of the dungeon [...]

Leave a Reply



Recent Posts

Recent Comments

Proudly powered by WordPress. Theme developed with WordPress Theme Generator.
Copyright © The Alexandrian. All rights reserved.