Ninja Burger and my first game in a while
Ayyavazi:
Hey everyone,
I played my first RPG in a little over two months, and it was fun, even if it wasn't spectacular. I gathered my fiancee, best friend and nhis fiancee together and we all played Ninja Burger. I was the only experienced role-player there, so I ran into a lot of interesting issues while explaining the game, and wanted some input.
First, when trying to explain the game to these new people, I didn't realize how important it was to explain what everything was for right up front. I dove right into character creations and read the house rules, but the players came away not understanding what their stats and skill masteries meant, how they interacted, or even what was expected of them as players. That is, they did not know how to ACT.
Now, first let me say that this was not set up to my liking. It was far from perfect. All of my handy charts and prep-work got left in the car by accident and couldn't be retrieved. I only had one copy of the book, and it was unmanageble at best to have pages everywhere. And we only had one character sheet between us and had to improvise. Ideally, I would have had notes, there would have been one copy of the book for everyone, and everyone would have read it ahead of time. Of course, it never works like this, especially with a group of new players.
What struck me about all this is that if you want a game to be accessible to new players, and people who have never role-played before, you have to present EXACTLY how the game works. And it has to be fast. Character creation for Ninja Burger ended up taking about an hour a half. It should not have taken more than fifteen minutes.
So, what I'd like to know is, how do you all create your games to be accessible to new players? What do you do to make sure your game can have been read by only one person in a given group and still be understood and playable? Do you have any reccommendations?
I'm trying to stray from the obvious response of, "Make a rules-light game" That won't help me if my game isn't rules light.
Anyway, on to the actual play, so you can see some of the obstacles.
We played the pre-made adventure in the book, but I decided to add a twist.
I framed the scene at the Ninja-Burger franchise instead of at the the fodtekken building, figuring my players would use some navigation skills to find the building and then go there. I ask what my first player does, and he just stared at me. He asked me what he should do. Bewildered as to why he didn't know, since I had laid out their mission, I laid out the following outline: Determine the location of the building, get there, get inside, deliver your meal undetected, accomplish your secret task, and then get out, again undetected. Another player remarked, "And all of those are one action each right"
I wasn't quite sure how to respond to this, since I had outlined how actions worked and everything. It all seemed so basic to me I forgot these people had never played and didn't have any context for understanding actions and using skills, or anything of that nature. So I changed tack. I said, ok player 1, I've given you an outline of what you need to do, now each step might be 1 or a hundred actions. You have to decide how much you are going to do with your turn, and remember, the more actions you take in a turn, the harder they will all be. After hearing this, he decides to hide and try to follow the first person to leave. Play moves on.
Player 2 decides to hide, figure out where the building is, and then go there. She succeeds on all of her rolls, and I move to Player 3. Player 3 decides to throw player one a bone and just figures out where the building is, and then going there. So, Player one follows.
I have them arrive on site the next turn, to speed things up. Players 1 and 3 arrive at the rear of the building and player 2 arrives at the front.
From here, play got gradually more informed and people started to understand the rules. This first turn took about half an hour or more. Every turn after that took between 1 and 5 minutes. The players kept asking me why the dice they had to roll changed, but around the fourth time that I said, "the more you do, the harder everything is on a one die for one action basis" (in varying ways), they got the picture. Player 3, the most uncertain of all the players at the beginning, ended up completing everything first, while player 2 came in 2nd, and player 3 failed to do anything useful at all, even though he understood the rules better than the others. Turns out Player 2 was fudging all of her rolls (perhaps I stressed the, "If you can get away with cheating, go rfor it" a biit too much).
More on this later.
Eero Tuovinen:
To answer your question, I manage beginner-friendliness in design by trying to establish the purpose of the game first and then moving on to the techniques, trying to ensure that the audience understands the reason for why each individual method used to play the game is in there. I've also experimented with relying on existing knowledge: my game Zombie Cinema is written to emulate boardgame rules conventions (and a boardgame structure in actual play as well), which would presumably make it easier to understand for people who are already familiar with learning boardgames from their rulebooks.
As for your account, that sure was amusing. I haven't read Ninja Burger myself, but that sure sounds like a pretty complicated game for beginners. Especially the fiction of the game seems like a big nerd culture injoke; I hope your players had the background to appreciate it.
Ayyavazi:
Thanks Eero,
But I was also wondering, how do you design the game so it can be easily explained? What if the new players don't want to read the book at all? How do you design a game that one person reads and understands, and then explains to the rest of the players? Thats the situation I am in right now. No one wants to put the time into reading 20-100 pages of rules just so they can play the game. They want me to be able to explain it and get to playing in about a half an hour, like a board game, actually. So, I'll try to get a copy of your game and see how it works. Thanks again!
--norm
Eero Tuovinen:
The boardgame thing is certainly one approach. Another is to build the game to cascade: make it so that a player needs to know just one thing to orient himself, then bring up the next rule when it is needed and so on. I find that traditional fantasy adventure games can do this sort of thing really quite passably if you use a light rules-set. Imagine, if you will, a game of something like D&D where you make it clear to the players that their task is to imagine this otherworldly dungeon environment and perform a mission therein by describing what their characters, brave heroes all, do. No other rules are needed to begin. Then when a character does something that triggers a rule, you can explain and demonstrate that rule: now you attacked a monster, this is how that works. Now you shoot with a bow, this is how it works. Now you negotiated, this is how it works. A traditional sort of GM-led game works for this purpose really well because their rules are random-access: they're just a pile of special cases you apply when particular conditions are triggered in the fiction. So really, if you remove the character creation from a traditional game (perhaps use a house system that can build the characters up as they are needed, or use pregen characters), you already have most of the tools for newbie-friendly gaming.
Of course, the cascade is a technique you can apply to explaining any game. I started a new Shadow of Yesterday campaign last weekend with some teenagers who'd never played the game before. I think it went pretty smoothly despite the game's somewhat elaborate character creation system - this was at least in part thanks to how I explained the game top-down, only zooming in to those rules that were immediately needed. The players could thus concentrate on only the choices and experiences that I found pertinent, moment-to-moment. This is often superior to trying to explain all of a game's rules all at once, at least if you yourself have a good sense of what people are supposed to think about and make decisions on in the game at a given point of play.
Ayyavazi:
Thanks Eero!
That is a huge help. Cascading the rules can be done very easily from a gm standpoint, but not so easily with certain games.
For example, the next thing I plan to play with this group is Dogs in the Vineyard. How do you reccommend I cascade that, and do the character creation as I go along? Should I give them pre-gen characters? Or maybe I could give them partially pre-gen characters?
That is, I make, say, one of each of the backgrounds, but only fill in the statistics. I leave all trait and relationship dice open to them, and let them build the character through play, starting with their intro scene. That would allow for a much more free-form character creation and let me explain the rules as we go along. Any suggestions on cascading those rules though? The conflict mechanics in Dogs are pretty much the only mechanics, and because of that I worry that once the characters start any conflict I have to say, "ok, heres how you reverse, heres how you dodge or block, and here's how you raise" which might take a while for them to grok.
Thanks again!
--Norm
Navigation
[0] Message Index
[#] Next page