Skip to main content

RPG Systems: An Analogy with UI Design



The current game in our weekly role-playing group is Deadlands. The previous game was Shadowrun. Both rule systems lie closer to the “chunky” side of the spectrum. Shadowrun has a particular reputation for its complex and somewhat cumbersome rules, and while Deadlands has less overall complexity, the system has a degree of granularity that interrupts play more often than it enhances narration. I enjoy role-playing games because I like participating in a good story. The rules system provides a set of constraints for the characters, the setting, and the conflicts. They help give the narrative structure, a background against which the story will take place. Too few rules, and telling an interesting and well-developed story becomes difficult. Too many rules tend to get in the way of individual scenes or events. With the right balance, it’s possible for the game master, usually me, to be sufficiently fluent in the rules system to resolve any conflict without extended consultation of one (or more) books. When I describe my ideal role-playing system, I am reminded of user interface design. A good user interface gets out of the user’s way. The user shouldn’t have to think about UI elements like chrome, throbbers, or buttons. Everything should just work, leaving the user to focus on tasks, specific applications, and workflow. Likewise, I like a role-playing system that fades into the background of the story. If the structure is too obtrusive, there is no room left for the narrative.

Since I’m a game master and not a game designer, I can understand that striking this balance is not easy. A rules system can provide an amazing formalization of the setting’s flavor, defining the boundaries of the ordinary and extraordinary for the setting. I sometimes find myself running chunky systems just because the setting is provocative enough to motivate a bit of extra study and note-taking before game.

Comments

Popular posts from this blog

The Incredible Lightness of Collaborative Consumption

Last week, we had to exchange our defective futon frame for a new one. The store didn't want to cover transport cost in either direction, so we had to figure out how to get our re-boxed frame from Mountain View to Los Altos. If we had a car, it would not have been very simple since we were aiming to buy a small sedan, nothing that can easily carry the frame and its box. Fortunately, we have a car sharing service that gives us access to a range of vehicles, including a van stored down the street from my building. After work, I grabbed the van, picked up the frame at our place, and then Tara and I drove to the futon to make the swap. I dropped off Tara and the new frame at our place, and then headed back to campus. On returning the van to its parking space, I hopped on a shuttle back to downtown Mountain View. We were able to do all of this because we're not tied to a specific vehicle for all of our transportation needs. The last car we owned was a van, and it came in handy o...

Carless in California

For various reasons, we do not own a car despite living deep in American car country. The reasons are largely financial; the cost of living in downtown Mountain View crowds car ownership out of our budget. We pay more to live in a pedestrian friendly neighborhood, so we are less able to afford a car. At the same time, I don't need a car to get to work, and Tara doesn't drive, so any car we had would sit in the carport most of the week. Combine that waste of resources with a reluctance to contribute to the Bay Area's traffic congestion, and forgoing car ownership doesn't sound all that bad. Car sharing services allow us to grab a vehicle as long as we plan ahead a bit. The Caltrain provides access to San Francisco. There are convenience stores and cafes in walking distance, so we don't feel the absence of a car too often. Last night was one of the few times where I did. After getting home from work, we wanted a dinner cheaper than nearby delivery options. The n...