Yes, a single game merits an entire post, because there’s a pretty good chance that this game will be your event’s problematic fave.
I’ll be honest, I liked Cards Against Humanity. Liked, past tense. When it first came out, all the expressions of bigotry and cruelty and general horribleness felt like “punching up”–making fun of people who actually believe and say all that stuff for reals.
I now believe that’s a rationalization, or at least it was on my part.
This is a bit of a tangent on something I touched on in the “Scheduled Games” and “RPGs” posts.
Successfully running an RPG at a convention is an art form (one I haven’t mastered). It’s loud and everyone’s under tight time constraints. (Dire Bear Adventuring Co. did an excellent job running D&D at the last few Hamacon events, if you want a good example.)
Here’s a few quick rules I use when running games at cons:
One of my main goals for Hamacon analog gaming was running events. This is typical when you’re talking about CCGs (tournaments) or RPGs (one-shot adventures), but I wanted to extend this to board games. Specifically, I wanted to introduce games that were fun or interesting, weren’t necessarily popular (i.e., you wouldn’t find on Tabletop or similar shows), and weren’t necessarily easy to learn (i.e., not Cards Against Humanity or Love Letter).
I updated one section of my “Hamacon Analog Gaming Bible” after every event: a list of people who had run something or otherwise provided content to the event. (This is the primary reason I’m writing a blog series instead of just making that document public in Google Docs.)
I am not a people person. I can handle all manner of technical details (like scheduling, teaching games, planning procedures, etc.) but as soon as I have to send an email or make a phone call I get antsy. Rest assured, I didn’t keep this contact list so I could send out an email blast as soon as I started planning.
The main purpose of your contacts list is to remember key details. Who are they? What did they do? How do you successfully get in touch with them?
If you’re running a free play board game library, you’ll need to have some sort of check-out system. It doesn’t have to be complicated–and it’s better if it’s not–but there’s a surprising amount of refinement you have to do to get it right.
My process uses two index card boxes labeled “checked out” and “checked in.” (If you haven’t read the “toolkit” post in this series, it will be helpful to cross-reference.) When someone checks out a game:
The next section of my “Hamacon Analog Gaming Bible” is a setup and teardown checklist. There’s nothing revolutionary here, but it’s helpful to remember a few things that will make your life easier down the road.
Over my years running Hamacon, I built up a Google Doc I called the “Hamacon Analog Gaming Bible.” These first few posts will be an adaptation of that. The first section is my packing checklist, so let’s start there:
Five years ago, I was offered the chance to run analog gaming for Hamacon, a small anime con run by some of my friends in Huntsville. My only qualifications were (1) I had played tabletop games at cons before, (2) I own a lot of board games, and (3) I was willing to drive a car full of those games 3 hours away.
It was a great experience, mainly because Hamacon had a dedicated, knowledgeable community running it, and that community had the freedom to do some interesting creative things.
In my case, I wanted to build an analog gaming room for people like me: somewhat socially awkward, and interested in trying heavier or offbeat games I might not be able to experience elsewhere. I didn’t necessarily achieve that. Even if I had, that’s a very narrow focus which isn’t necessarily serving other attendees wants.
While I’ll likely be on a con staff somewhere in the future, I’m not currently, so I don’t feel like I’m revealing con secrets by adapting my con checklist (and other lessons learned) into a blog series. Hopefully, someone can benefit from some things I learned–or at least avoid some things that I failed at.
I’ll also mention that MTAC and Momocon were major inspirations for the way I ran Hamacon analog gaming. Which is to say: if you like tabletop games, they’re cons you might want to check out.
Posts in this series:
A few months back, I played around with (yet again) rebuilding a half-finished Metroidvania-style game I’ve played around with off and on over the years.
One of my goals in this experiment was to use base Unity functionality as much as possible, replacing 2D Toolkit and custom systems as much as possible. One of the prime candidates for such a rewrite was the menu system:
If it’s not immediately obvious, that’s essentially a vertical menu with items that have horizontal behaviors. When “Equipment” is selected, you can choose an item to use or equip on the horizontal axis. When a volume slider is selected, you can adjust the value with the horizontal axis.
Importantly, the game’s intended to be played with a gamepad, so I didn’t want the presence or absence of mouse or touch input to affect this behavior.
Unity UI navigation is pretty smart, and got me most of the way there. If you’ve focused on mouse/touch interface when building your UI, good news: if it’s a grid-ish format, it probably works the way you’d expect. That’s thanks to…
