The Mysterious Lever

Tuesday, July 18, 2017

Mechanics for Both Sides of the Table

Game Masters do a lot of work. They are the ones doing the prep, adjudicating fairness, and roleplaying a whole world, while players show up to game day with a character sheet and some dice, there to relax and have fun. So, with Hostargo, I want to take as much pressure off of the GM as possible. But recent playtests have shown that is it possible to go too far in that direction.

One of the main mechanics I was excited for in Hostargo was the crash. When players failed an action, this was an extra die roll that they made to determine -by how much- they failed. This was a fantastically arbitrary number for myself running the game, as it gave me some input on how to describe the outcome of failures. However, its arbitrary nature also aggravated the players, because regardless of their initial roll, their character's skills, or the current situation, the crash roll was an independent determinate of their fate.

This simple but prominent mechanic has stuck around in Hostargo for longer than it should have. It had a clear negative effect on the game, but I was dragging my feet in changing it because it's purpose was really to make the GM's life easier. I couldn't really see, from only looking at my side of the table, how much of a problem it really was. It was under the players' skin. Not everyone could even pinpoint what they didn't like about it; after all, it made otherwise "nothing" rolls into "something interesting probably happens". After enough feedback, however, it has become clear that this (and some other mechanics like it), need rework.

There are plenty of ways I can deal with this mechanic. I can address its symptoms, or rip it up from its roots. The more important lesson here though, is that I need to pay closer attention to how each of these mechanics is affecting both sides of the equation. Especially since Hostargo is an asymmetrical game, there's plenty of room to ensure each mechanic not only does its job, but feels good to the people at the table.

Monday, July 10, 2017

Working with Feedback

Playtesting is a lot like playing an RPG. Each time you see your carefully laid out plans in action, there are feelings of pride, excitement, and anxiety. But just like the most carefully constructed strategies - there's always a wrench that comes flying from some portal to a plane of existence you didn't account for.

A strenuous amount of effort is required to level up in the RPG of playtesting. The reward cycle is long - from creation, to execution, to the extra analysis that is required to really dig up and polish the gems you're actually looking for. Along the way, you'll encounter a variety of challenges that you aren't always prepared to handle. This comes in the form of players, and the extremely wide variety of opinions that they hold. In order to deal with this variety, it is paramount to remember: not all feedback should be taken as a call for change, and just as importantly, no feedback should be fully ignored.

I will reiterate what I'm sure a lot of you have heard a million times before: do not take every piece of feedback you receive, good or bad, and treat it as gospel. You must keep your own design goals in mind; for mechanics, for flavor, and for feel. Do not let any single piece of feedback steer you away from a "bad" idea or solidify any idea as "good". Each piece of feedback must be taken:

  • In context of the playtest (the adventure, the group dynamics, the general mood).
  • In context of the player (what other types of games do they like, and why)
  • In context of your design (how does the idea in question apply to your design goals)

Beware - do not let yourself easily dismiss a player's thoughts and feelings. Listen to them, talk it out with them, and gather as much information as you can. Make them feel validated in their opinion in order to receive it in it's raw, pure form. While small, each playtest is the the only sample data you have. These are the players that chose to sit down with you at your table and play this probably broken contraption you've constructed for the sole purpose of giving you feedback. Do not let that go to waste.

Even if you take absolutely no action based on the feedback of a player, at the very least you need to understand where the feedback came from. Find out what the player was thinking and feeling at the time. Find out what else was going on. Find out from the other players what they thought about the same situation; it's important to get different perspectives. All of this allows you to analyze the feedback against the contexts mentioned above. With it, you are better equipped to handle your game in environments where maybe it doesn't fully shine. Better yet, you may just be able to let go and realize what does actually need to change in your game for you to achieve your initial goals.

Learning when and where to act is the key to successfully incorporating feedback into your games. With each playtest comes experience. With each experience point you will grow in power. Do not let that power get out of hand - use it to adapt to the world you live in in order to mold the world you are creating.

Friday, February 10, 2017

Priority First

I have been slacking. I know this. But, there's a lot of things happening for me right now, including a new job and getting married... two HUGE life changing events haha. So, I'm taking it easy where I can, and that includes hammering out designs.

I'm looking forward to a variety of PS4 games this year, as well as the Nintendo Switch. But, after the wedding in June, I should have things settled down enough to start really rocking again. In the meantime, I plan on continuing to work with my artist(s) and other designers to hash out some of the small stuff before I hit the hard work again.

Cheers!