So I am GMing DW games for some of my friends.

I have combat figured out.

Primary mission objectives, and missions arent too much of a problem.

What I am really having a problem with is creating meaingful choices for my players. Im trying to create choices that are neither right or wrong, but have a meanful impact either right then, or at a later time. I also want the choices to cause some conflicts or indecision within the group.

I'm trying to also have some of these choices come up in an organic manner. So it doesnt end up being just choice A, or choice B, but instead a whole range of choices that the players figure out instead of just being choice A or B that i present to them.

Does anyone have any tips, or suggestions on how to help generate choices for the players?

Thanks,

Skunk

Skunk Bottom said:

Player driven games are the best games in my opinion. In order to deal with them you need to keep the game simple. Don't try and plan for everything. Here is what I like to do. Create a flowchart and answer simple yes or no questions. I have actually designed a sheet for this. I will start another post about my "Four Hour Frenzy" session design but creating a flowchart can help immensely.

1. Inserting the players into your game. Give them options. Allow them to choose how they will insert themselves into the mission. In the flow chart just ask yourself one question. Do they land at the insertion point, yes or no? Do not overcomplicate it. Come up with an outcome for yes and an outcome for no. What would happen if they didn't land at the predetermined site? If they did?

2. The hardest part is getting players to begin narrating the story by their own actions. Here is one of the hardest things for a GM to do - design your game around the characters. Always find a moment where every character can shine through non-combat. It can be very simple too - a single skill use can get a character involved.

3. Complicate the Mission. Design a simple mission to begin with. Then through choices of the players - make it complicated. All of a sudden through their choices the mission is now a race against time. Also, avoid making them afraid of performing skills. This can kill a game. I never punish skill failure in my games unless it is a really high degree of failure. The skill might fail but I don't create a situation that can kill the player because of the use of a skill.

4. Evolve your game from a simple template as the mission progresses. Again, simplicity is the answer. Keep it very simple and then let the players determine everything about the mission. Literally, let them try and create secondary objectives themselves. Give them a primary objective, that's it. Let them decide every facet of the mission based on intelligence they have, operational reports, etc… Let them do your work for you. They will and they will like it.

Player driven games once they pick up steam the players like it. Never control the game. As a GM, you are the world not the storyteller… they are the storytellers. I really try to avoid having the person in charge tell the PC's what to do. My Deathwatch PC's are on their own with a specific overall mission - to locate and destroy the orc supply chain and cripple the orc Waargh! so that Imperial forces can win the war. So, the players basically find their targets by themselves and decide how to approach it. They are on their own with a few servitors, crew and an overall order. They are getting a lot of attention though, so in my head (and with a flow chart) I have started determining how I am going to strike back at the Kill-Team. Even then, they will have to decide everything. Also, don't play a character. Playing NPC's here or there is great but I completely avoid playing a fellow battle-brother in my games as it is too easy to throw the players in the right direction. I think they should expect that some choices will backfire on them and complicate the game.

Thanks for responding. I really like your idea of making it all player driven. I was struggling with how to plan for that, but the idea of a flow chart has completely fixed that problem for me. Making it player driven and following suggestions, I think is going to make my job a whole lot simpler.

Thanks-

Skunk

just be prepared for the players to go off your flow chart…..(one of) a gm's most valuable skills is being able to wing it…..

Zappiel said:

That's pretty much why I like to keep it simple… my flowcharts are pretty much just a yes/no progression… Playing by ear is truly the only way to GM a player narrative focused game. Players WILL go off your flow chart, you can count on that… in a player narrative they are supposed to. I like to use simple outlines with ideas that can happen.

The best thing you can do is have stat blocks for enemies on hand and a general idea of how you want your adventure to progress thematically. I like to think of an adventure theme more than anything else… should the game be a horror/survival type mission? Combat focused? Perhaps investigation? Stick to simplicity and your players will create a complicated game… try to be too complicated and you will have a mess on your hands :)

Mindforge said:

I totally agree. The success or failure of skill checks does not determine if the story goes on or is stuck. It simply says how the story evolves.

Cheers,

-- TechVoid