Post is part of the blog bandwagon about maps. You sit down ready to play some sicko dungeon ass dragons, all hyped up for the first session. The referee asks everyone to turn around while he preps the table. When you turn back, you see a map. At least, you think it's a map. A single hex is revealed, with a marker supposedly representing the party. Everything else is covered in black construction paper. With a wry smile, the referee asks, "Where do you want to go?" After a brief pause, someone says, "Uhh... north, I guess?" I love maps as much as the next cat, but I think a map has to serve a purpose in play. A map isn't automatically useful because it's beautiful or impressive. Those things can help, of course. But the maps I want at my table are the ones that help us understand the situation and make meaningful decisions. A map can serve different purposes. It can support the backend, frontend, or runtime of your game. It can store the truth of locations for the referee, give visual…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.