Rating: 4 of 5 stars
Details: Instead of everybody doing background stories on their own, let others influence some part of it and create a connection between characters as a side effect. One way to achieve this is to frame some questions everybody has to answer about the character of his left or right neighbor and share that information with that player.
Some examples:
Your character knows a secret of the neighbors character. What is it?
Or the variation: The neighbors character knows a secret of your character. What is it?
What does your character not like about the neighbors character?
How did your character met the neighbor's character?
And since there has to be an explanation how that character knows these things a connection between characters is created.
The technique is not restricted to character creation. It could also be applied after some time thereafter. For example by saying that the group has spend some time together and the members have learned more about each others during encounters.
Usage in the session: When we played a one-shot we used this to create the some background for the characters.
Impact on our session: It was fun to see how different the players did answered the questions and most answers were original and made a good base to start the game with. Also did the players get into the mood for more than only some combat encounters and we had some descent roleplaying.
Advice: Whenever I am in a game with new characters I would like to have at least one around the table question. Why?
For a one-shot this helps to create a bit of background story since most players probably would bother to make up a background for such a game.
And for a ongoing game it helps to create connections between characters. And the players do learn about each others background stories. Especially questions about secrets could be the cause for some interesting developments in game. I had enough campaigns in the past where background stories did contain some hidden facts about a character but they never came up in the game. But since one in the group knows about it, if using this technique, it is more likely to come up and have some impact on the game.
This should not replace the creation of background stories by each player but it is a nice way to contribute to the stories.
The questions/answers should be framed in such a way that the answers do not have to much impact on one characters background story. If a player has a clear vision of his character and such an answer would force the player to go into a direction she or he does not want to the player should be allowed to either ignore it or to ask for another answer.
And I would also advice against to many questions. One or two (one for each neighbor) is enough.
Sunday, January 24, 2010
Thursday, January 14, 2010
Lesson Learned: Hard (combat) encounters are the best
Essence: Easy combat encounters (less then the level of the party) are almost always a waste of time. Players tend to notice real quick whether enemies are a real threat or not and they do not feel powerful or challenged if the defeat a group of enemies without any resistance.
Encounters of the same level or one level higher are good to prevent that a group gets frustrated after a very hard combat or if they have lost fight.
But the hard combats (two or three levels higher than the party level) are the fights the players keep talking about even after the encounter and that stick in the memory.
Details: Currently I am running the Pyramid of Shadows adventure with a group of 5 players. The adventure is for level 7-9 but since the group was already at level 8 when they entered the pyramid most combats are one level less or the same level as the level of party.
The first couple of encounters I ran as described in the book . But they were only fun if one of the players was missing (which often was the cleric). The combats became a kind of routine and after we were finished playing the talk about the game was short if any took place at all.
Only when I started adapting the encounters and made them hard it felt as if the group became alive again. The players stayed more focused during the game and they time we talked after the game became longer. And believe me nothing gets you the attention of the player more then reducing the hp of his character to zero or bellow.
From all the encounters we had in the last 1 1/2 years I only can remember the really hard once.
Advice: Keep track of the healing surges the characters still have. If one ore more characters only have few surges left be weary with hard encounters. You want the encounters to challenging but not deadly.
Adapting encounters in D&D 4E is really easy. If I do not find the time to adapt the combats before the session I add another monster or so on the fly. But that often does not make the combat challenging enough. Currently my preferred way is to take the monsters as described in the adventures and increase the level with the help of the Monster Builder which takes me about 5min per encounter.
Encounters of the same level or one level higher are good to prevent that a group gets frustrated after a very hard combat or if they have lost fight.
But the hard combats (two or three levels higher than the party level) are the fights the players keep talking about even after the encounter and that stick in the memory.
Details: Currently I am running the Pyramid of Shadows adventure with a group of 5 players. The adventure is for level 7-9 but since the group was already at level 8 when they entered the pyramid most combats are one level less or the same level as the level of party.
The first couple of encounters I ran as described in the book . But they were only fun if one of the players was missing (which often was the cleric). The combats became a kind of routine and after we were finished playing the talk about the game was short if any took place at all.
Only when I started adapting the encounters and made them hard it felt as if the group became alive again. The players stayed more focused during the game and they time we talked after the game became longer. And believe me nothing gets you the attention of the player more then reducing the hp of his character to zero or bellow.
From all the encounters we had in the last 1 1/2 years I only can remember the really hard once.
Advice: Keep track of the healing surges the characters still have. If one ore more characters only have few surges left be weary with hard encounters. You want the encounters to challenging but not deadly.
Adapting encounters in D&D 4E is really easy. If I do not find the time to adapt the combats before the session I add another monster or so on the fly. But that often does not make the combat challenging enough. Currently my preferred way is to take the monsters as described in the adventures and increase the level with the help of the Monster Builder which takes me about 5min per encounter.
Friday, January 8, 2010
Improve your GMing: The Mountain Witch Trick
Rating: 5 of 5 stars
Details: I have heard about this the first time in a podcast (if I remember which I will add the name and URL) and a quick google will tell you that it is a technique described in the game 'The Mountain Witch'.
Instead of the GM telling the players a background story or describing a scene a player does it. This is done by the GM by telling either what a specific character perceives or how he reacts to a certain scene and asks the player why.
Usage in the session: The party was confronted by a group of mercenaries lead by a dragonborn. I told a player, who also plays a dragonborn, that he knows the leader and remembers him as shady, untrustworthy individual. And then I asked why his character did know him and where from.
Impact on our session:The result was way better than expected. The player did not only instantly tell a good story but also did the other players learn more about the background of that players character as well. He did such a good job that the others did not even noticed that he made it up on the fly.
The now established personal relationship motivated the player to some roleplaying which lead to more fun for everybody. In the combat that eventually followed the player insisted that he would battle the leader alone and an exchange of insults did take place which added flavour to the session we seldom had.
Thanks to the usage of Mountain Witch I had the best session as a GM for months and I think my players had a good time as well.
Advice: Even if the Mountain Witch is a great way create to instantly involve characters or to add elements to a scene you as a GM would not have thought of I would not use it too often. Why? Taken to the extreme it might get silly. Think of a dungeon delve where every group of enemies the party meets has at least one member which is personally connected to one of the characters. Which is more than implausible.
But if you use it maybe once per session and in a creative way this trick will definitely improve your game.
Details: I have heard about this the first time in a podcast (if I remember which I will add the name and URL) and a quick google will tell you that it is a technique described in the game 'The Mountain Witch'.
Instead of the GM telling the players a background story or describing a scene a player does it. This is done by the GM by telling either what a specific character perceives or how he reacts to a certain scene and asks the player why.
Usage in the session: The party was confronted by a group of mercenaries lead by a dragonborn. I told a player, who also plays a dragonborn, that he knows the leader and remembers him as shady, untrustworthy individual. And then I asked why his character did know him and where from.
Impact on our session:The result was way better than expected. The player did not only instantly tell a good story but also did the other players learn more about the background of that players character as well. He did such a good job that the others did not even noticed that he made it up on the fly.
The now established personal relationship motivated the player to some roleplaying which lead to more fun for everybody. In the combat that eventually followed the player insisted that he would battle the leader alone and an exchange of insults did take place which added flavour to the session we seldom had.
Thanks to the usage of Mountain Witch I had the best session as a GM for months and I think my players had a good time as well.
Advice: Even if the Mountain Witch is a great way create to instantly involve characters or to add elements to a scene you as a GM would not have thought of I would not use it too often. Why? Taken to the extreme it might get silly. Think of a dungeon delve where every group of enemies the party meets has at least one member which is personally connected to one of the characters. Which is more than implausible.
But if you use it maybe once per session and in a creative way this trick will definitely improve your game.
Initial blog
Who is this blog aimed at? Me. Why? Because I have been following RPG blogs, podcasts, tweets and so on for some time and have heard/read about good RPG ideas and tricks to improve GMing but I tend to forget them.
Therefore I plan to gather good tricks, try to use them during my weekly D&D 4E sessions and document if and what impact they had on the gaming experience.
My group is more into combat and cares less about character development or about telling a story of their own. That's why I am looking not only for ideas and tricks that will increase the fun we are having when gaming but especially for those which will add more roleplaying elements to our sessions.
And maybe I will improve my English writing skills as a side effect of this blog.
Therefore I plan to gather good tricks, try to use them during my weekly D&D 4E sessions and document if and what impact they had on the gaming experience.
My group is more into combat and cares less about character development or about telling a story of their own. That's why I am looking not only for ideas and tricks that will increase the fun we are having when gaming but especially for those which will add more roleplaying elements to our sessions.
And maybe I will improve my English writing skills as a side effect of this blog.
Subscribe to:
Posts (Atom)