Wednesday, September 7, 2011

Role Playing Games: Or RPGS?

There is a difference between RPGs and Role Playing Games. RPGs are more computer/console-based, and tend to waffle between one of two different tropes: you wander around randomly fighting things to gain experience to unlock greater powers, or you go from one battle in a 'chain' to the next until you reach the next portion, gaining amounts of XP along the way that you can then use to purchase whichever skills you like.

Sounds kind of familiar, right? But these games can be very different from Role Playing Games. Or, maybe even better, Tabletop Games.

Tabletop games evolved from old wargamers wanting to add a little extra something to their weekly war sessions - stories of how their figurines had gotten where they were, eventually evolved into something different from the norm - the Role Playing Games we know and love today.

It has since inspired entire generations of games made in similar veins, but there is still a distinct divide between what we experience on computers than what we experience at a table (or even virtual tables, if you will). Much of it is often attributed to not having an active gamemaster who can make up rules on the spot, or being able to change the game or even completely reinvent it as needed. But that's not the only place this divide comes into play: the design philosophies can often be different as well.

Now, many times people will argue that they are 'just the same'. But let's not lie to ourselves. There's a tremendous difference in the design philosophies between Final Fantasy X and our tabletop experiences. Take any random-encounter RPG - yes, old-school D&D has random encounter charts, just like most other RPGs. But those RPGs, you expect them, because they go by so quickly. Tabletop, however, is far more immersive - yes, you can have those random encounter charts, but you are in that area for a reason, and then suddenly TIGERS EVERYWHERE. What do you do?

There's a good point to understanding where this divide comes in, because as a GM, it's not just your job to set up a random encounter chart and go wild with it. It has to have a purpose and a reason. Let me share with you one of my experiments from my post-apoc future game, Roguelife.

The group was going to explore an abandoned city, looking for Quest Item X. Of course, X was something they had no idea where to find! It being a big city, I wanted it to be somewhat more old-school adventure - a bit of a departure from the traditional 'hallway segments', where the group goes from one battle to the next until they finally reach the end.

I set up a very large spreadsheet, which worked extremely well. It listed different building types, different creatures that could appear in those types, and depending on the sort of building it was (and it's size), you could expect to find a predetermined amount of loot within those buildings (if you were clever enough). This was awesome because it could generate some truly interesting things - in one building, they stumbled across a group of mutants who were being 'purified' by extremists - realizing they couldn't fight such a large battle, the group wisely opted to try looking elsewhere. In another building, they went all the way down to the ground floor, only to find an entire *herd* of Dire Caribou defending themselves from zombies. Successfully, I might add (they were, after all, DIRE Caribou).

Things like that can make for amazing gameplay sessions, but half of it is being able to know how to read those charts and react to them on the fly - how can you pull these elements together to create a similar scenario that the group may have already encountered, but adding some kind of twist to it? Another one had them trying to get into a gas station that was surrounded by zombies and... a DIRE BEAR. Oh man that bear almost tore them up, but they managed to bring it down and save the man inside.

Of course, since I made the chart, I already had an idea how these things could fit together. All in all, it was an attempt to make a tabletop version of a Roguelike - one that worked amazingly well.

So consider the type of game you are running, and the feel you want to give it. Is it a high-stakes game, where there is a clearly-defined goal and maybe even a clearly-defined path to achieve it? Or are your players looking for something more adventurey, where the destination is not as important as the journey to reach it?

Think it over. Talk it over with your group even. You might be surprised at what you can learn.

No comments:

Post a Comment