Reply to thread

Message: <blockquote data-quote="TikkchikFenTikktikk" data-source="post: 5330382" data-attributes="member: 67494">Since reading <a href="http://www.movieline.com/2010/03/david-mamets-memo-to-the-writers-of-the-unit.php" target="_blank">David Mamet’s Master Class Memo to the Writers of The Unit</a> I essentially run my games as a succession of skill challenges.(This, by the way, sums up why I ****ing hate "roleplaying" buying torches. Ugh. There should very rarely be drama involved in going to the grocery store.)Do not tell the player's they are in a skill challenge. Give them a goal, then give them opportunities to fail in pursuit of that goal. Use skill checks as the mechanic to adjudicate whether they are getting closer to their goal or failing.Make sure you are using the updated skill challenge rules from the Rules Compendium/Essentials. It has done away with the "three strikes and you're out" rule in favor of essentially saying (hah!): failure should have negative consequences.Running skill challenges well is an art form. If you want to get good at an art you must practice.Your giant skill challenge is very ambitious. If you haven't been using many skill challenges up to this point, it is probably too ambitious. If you start using the skill challenge framework more you will be more comfortable when you finally drop this awesome scenario on them.Darn, I was going to make this short. Oh, well. It's free advice!</blockquote>