How Do You Hexcrawl?

Note: This post, as well as the seven others which will follow it next week, were originally written about two years ago. They were intended to be nothing more than a short series, building on my then-popular Cool Stuff in the Wrong Direction posts. The idea quickly caught fire in my imagination, and I started to develop and expand it beyond the original 8-post run.

Before I knew it, I’d written an entire book. Literally. For over a year now, I’ve had 150+ pages sitting on my hard drive while I work on gathering art and saving money to pay for a proper layout. My plan was to hold these posts in reserve until it was time for a big marketing push. The thought was that I’d post all of these, then after the last one went up I’d say “Didja like that? Well guess what, it was just the first draft of a book that is on sale right now!”

I don’t think it was a terrible plan, but the further out I get from originally writing these posts, the rougher my rough draft starts to look. At this point I don’t think they’re very representative of the quality of the book. Which isn’t to say they’re bad posts–I wouldn’t post them if I thought they were bad–but I don’t want to hold them in reserve any longer. It’s time to get these out of my drafts folder, and out into the world.

Enjoy!

It’s entirely possible that I’m just stupid. There have been many times when I felt certain that what I was looking for didn’t exist, only to be proven humiliatingly wrong the moment I opened my mouth about it. Having said that…

I’ve never seen a good explanation of how the nitty gritty of hex crawling is supposed to work. In the past when I’ve said this in a public space, I’ve been given links to some ostensible explanation. However interesting these links might be, they tend to focus on how a hex crawl ought to work in theory, and have never satisfied my curiosity about the practical, at-the-table mechanics of running one. I’m sure there are people out there who know exactly how a hex crawl should run in practice, but unless any of them want to explain it to me, I need to make the rules up myself. Just for the sake of being comprehensive, I’m going to start with the absurdly basic stuff.

Each hex is 6 miles across. The terrain type shown on the space accounts for the majority of the hex’s terrain. But just because a given hex shows plains doesn’t mean you can’t find a copse of trees there. Plains dominate the space, but the world’s environs aren’t actually broken down into hexes. The hexes are an abstraction. The straight lines between one environment and another actually represent a gradual, uneven transition. Saying “The trees become more spares, giving way to plains over the 6 hours you travel West” is fine. The map itself may be ugly, but since the players will be describing their movement in terms of how many hours they walk in a given direction, a more detailed map doesn’t really improve your ability to manage the campaign much. Though, there’s no harm in taking a prettier map and slapping a hex grid on top of it, that works just fine as well.

It has occasionally been pointed out that a 6 mile hex is ludicrously huge in size. Video games noted for their vast playing space, such as Oblivion or Skyrim, are small enough that the entirety of the game world would fit within a single hex. This vastness is actually beneficial in several ways:

• It means that no matter how often the players travel through a given hex, you can always justify finding something new there. Barring significant effort, this ensures that a given wilderness environment never becomes safe and mundane.
• The math for converting hexes into miles is very simple, if for some reason you ever need to do that.
• It allows you to portray vastly different political situations, environments, and cultures, without forcing you to manage an unwieldy amount of game spaces.

Moving on: the most confusing thing about hex crawls for me has always been how to translate what the players say into what is happening on the hex map. In the past I’ve tried giving players a blank hex grid of their own so they could fill in spaces and tell me which edge of the hex they wanted to explore out of, but I don’t like how this feels. Players already have an idea of how to communicate movement in the wilderness using the cardinal directions. The hex map can be a great referee tool, but I’d prefer not to make the players think about the world in terms of hexes. Unfortunately, cardinal directions don’t always give you a good idea of what hex the players will move to.

If your map were drawn on this hex grid, it would be easy to know what to do if the players say “we go East,” or “we go West.” But what about the North/South axis? Do you choose to skew them slightly to the East, or slightly to the West of where they wanted to go? You could just determine it randomly, then remember to skew back in the other direction if they keep going. That would keep them moving in vaguely the right direction, and is probably the best choice for maximum simplicity. It’s not unreasonable to think they meander a bit as they travel.

If you’re more ambitious, you could try to keep an idea of where your players actually fall within their hex. This requires more granular tracking of how far your players move at a time, but it does have the benefit of making their time expenditure more meaningful, and of making it more clear what hex to move them into next. The geometric simplicity of a 6 mile hex, along with the fact that LotFP’s daily movement rates are all divisible by 6, should make this a feasible task. Though I can’t imagine doing it without constantly marking little travel lines on my hex map. I’d probably tend towards the simpler option myself, at least until I’m more confident running hex crawls than I currently am.

Which brings us to terrain difficulty. You can’t just have characters moving through mountains at the same speed they move along a road. Some hexes are more difficult to get through than others. There’s a whole range of methods, with varying degrees of complexity, that you could use to determine just how much travel is slowed on rough ground. For now, I’d like to keep it super simple. There are three types of terrain:

• Normal. Players move at a normal rate through most terrains. If it doesn’t fit into either of the other categories, it’s normal.
• Difficult. Players move at half speed. This is anything that would present a significant challenge to movement, like mountains or swamps.
• Roads. Players move twice as fast so long as they’re walking along a road.

Hand in hand with terrain type is encounter checks. How do those work? How often do you check for them? Again, I say keep it simple. Check once per hex. Twice if the hex’s terrain is difficult, and once every second hex if the players are on a road. (That’s once every 6, 3, or 12 miles respectively). Commensurately, I’d probably place relatively uninteresting encounters along the roads. (After all, anything interesting will have been found), and more interesting encounters in difficult terrain. That creates a nice risk-reward dynamic between fast travel with no loot, and slow travel with tonsaloot.

So what are these encounters, and how are they determined? I’m a big proponent of Brendan’s overloaded encounter die. In ORWA, I use three different encounter die charts based on how frequently a check is required. This is what I use for my 4-hour checks, which I think should translate well to once-per-hex checks.

1. Encounter.
2. Location.
3. Spoor
4. Rations.
5. Lost
6. Safe

Encounters are stuff like wandering monsters or NPCs. They’re rolled on an overall list that covers multiple hexes, like an entire cluster of forest hexes, or maybe even just a whole hex map. There’s between 4 and 8 entries on this table, and nothing is too specific. I don’t want to have to restock it. The point of the encounter table is to provide a sense of cohesion. No matter where you go within the domain of the Goblin King, you might encounter a goblin war party.

Locations are the beating heart of the hex map. They’ll require some extended discussion, so I’ll do that below.

Spoors are hints. They’re footprints, eggs, nests, or a dropped note. They let you know that something exists nearby which you haven’t encountered. When you roll a spoor, you should flip a coin to determine whether it’s an encounter or a location, then roll on the appropriate table to find out what the spoor points to. Once you know that, you can tell the players what kind of spoor they find. Then it’s up to them to interpret it, and choose how to respond.

Rations means the players are tired and need to rest and eat. If they don’t, they’ll take whatever penalties tired and hungry characters suffer. (Personally, I call it a flat -1 to all rolls). This result can be dismissed if it comes up more than once in rapid succession, but having it attached to the encounter roll is a lot easier than tracking rations separately.  A+++++ highly recommended.

Lost means that the players are lost. The referee doesn’t tell them that they’re lost, but you roll 1d6 to determine which direction they start moving in. Of course, if they’ve got some means to avoid getting lost, consider this a “safe” roll. Means do avoid getting lost would be following a road or river, having a guide who knows the area. or even just having a compass.

I’d actually be interested in exploring the idea of getting lost in greater depth, since it’s fairly easy to avoid it. Maybe compasses should be a lot more expensive than they usually are? A high level luxury, perhaps. But that discussion is for a different post.

Safe means nothing happens. Sometimes you move from one hex to the next hex without anything exciting happening.

Alright, so, Locations. Locations are tied to individual hexes. When the encounter die rolls a location, you have to check to see what hex the players are in, and then what locations exist in that hex. If a hex map were a dungeon map, the locations would be the room descriptions. But unlike a dungeon, the “rooms” are so vast that there’s only a small chance of seeing the description each time you pass through a hex.

Locations can really be anything. Of course they can be actual locations, such as villages, dungeons, altars, statues, magic trees, whatever. But they can also be something more transient. They can be wandering wizards, recently summoned demons, or a big scary monster. These are things you might normally think of as encounters, but they’re unique, so you don’t want to put them on the encounter list, which is meant to be more general.

How many locations should a hex have? From experience I can confirm that it’s easy to underestimate just how large an undertaking stocking a hex map really is. There’s no need to create a table of locations for each hex. It’s not like players are going to spend a ton of time exploring a single hex and run through all your work. Hexes are made for passing through. After a session of hex crawling, you can just go back through and restock all the hexes where the players discovered locations with new locations. That keeps the work a lot more manageable.

If you want to be safe, you could push it and put two locations in each hex, but honestly I think it’s fine putting just one location in each. Though that’s not to say you should feel bound by whatever your standard is. If one of your hexes is special for some reason, put as many locations in that hex as you like. Overall, though, it’s best to keep the standard number of locations per hex as low as possible.

Finally, what other information should be included in a hex crawl? I’d probably throw an overview in the front with a brief description of the region, its history, and the forces that are at play there. Something to keep short and sweet, since most of the flavor should be communicated through hex content and encounters. This is also where I’d make note of any particularly important and well known locations, like a large city in Hex XXX. The sort of thing everyone the players meet would be aware of, and which the players themselves might be on their way to reach.

I’d also write about any notable environs, particularly if they span multiple hexes. If the cluster of 8 forest hexes in the south of the map is “The Forest of Doom,” where gremlins sneak about through a persistent chest-height pink mist, that’s something the referee should be warned of up-front so they know to mention it as soon as the PCs enter that hex, even if they don’t think to check the hex’s information.

That’s everything I can think of for now. I don’t know if this has been a useful document for anyone else, but I have to say the process of writing it has made me feel more confident about preparing and running hex crawls, which is something I’m in the middle of doing right now.

Next week will be the first in a 7 part series of posts where I stock a hex map. In point of fact, this post started its life as a footnote on the first entry of that series.

It got a little out of hand.