After Sundown 1e

When you use a skill, describe what it is that you intend to do to the MC, and then between the two of you determine an acceptable Skill and Attribute to use. Remember that the attribute being used in an action determines what kind of people are naturally talented at that kind of action, not on what kind of character is generally good at a skill. For example, in the general running of a power plant one might expect that a "smart" hero would be the one for the job, and thus a good standby check to make for actions from shunting power away from the financial district to increasing power yield might be Logic + Operations. But in the specific case of getting the emergency valves opened during an overheating event you might expect a "strong" hero to be the one for the job, and Strength + Operations might be called for instead (those valves can be hard to turn).

The next thing you do is roll your dice, counting every 5 or 6 as a 'Hit'. The number of hits you get determines how awesome you did, with this representing overall success or not depending on how awesome the specific thing you were attempting to do was. Doing something incredibly awesome when the task at hand is something like "bake a cake" is potentially delicious, but often fairly inconsequential. On the flip side, if the goal is to do something of awesome difficulty such as leap into an open window on a moving train, the results will be unfortunate if the level of success attained is merely normal.

Buying Hits: When a character is not under any particular threat or pressure, they may elect to forgo the process of actually rolling dice and simply get one hit for every 4 full dice in their dice pool. This process of "phoning it in" gets a character less awesomeness than had they legitimately tried, but it has a strong tendency to work if that's all that is required.

It is important to note that normal humans often have dice pools of 4 dice or less on tasks they do frequently. So when a supernatural critter throws down on a task with 12 dice or more that really is an incredible thing to watch. Such characters can literally phone in a TV quality performance and the like. MCs should not become jaded and allow success inflation to cheapen the actions of characters with super human dice pools. Characters who can lift and throw motorcycles genuinely can expect to casually kick in locked doors. The fact that success is practically automatic for these tasks should not be resisted, but rather embraced as a fact that is itself impressive and magical.

Predictable Failure: Sometimes a character will be struggling under enough penalties that they don't have a dice pool at all. In these instances, the character is going to get zero hits, which means that absolutely nothing they do will be awesome. They can still stagger down the corridor or open a door, but as soon as a stunt requires even one hit they are going to fail unless they are a Luminary who can spend Edge on the problem to get some dice and a chance.

Extended Tests: Some actions take an expected amount of time. If a character gets the requisite number of hits, they succeed in the expected amount of time. If they get more than the requisite number of hits, they may complete the task well ahead of schedule. For every hit made in excess of the minimum, move to the next lower amount of time on the time chart. If a character fails to succeed, they may retry, but only after having put in the normal time into the first shot. So for example: Mina is attempting to paint a house (Strength + Artisan, 1, 2 days) and gets 3 hits. Since she got 2 more hits than she needed, she can go to the next lower time period twice, bringing the time frame down to five hours.

• Century
• Decade
• Year
• Season
• Month
• Week
• 3 Days
• 1 Day
• 5 Hours
• 1 Hour
• 20 minutes
• 5 Minutes
• 1 Minute
• 1 Round
• Simple Action
• Free Action

If you're about to launch a friendship speech, please don't.

When more than one character throws their weight into a project they can achieve results that are more awesome and in less time than what either character could achieve alone. However, the game mechanics completely break down if you just add the dicepool of one character to another. What is done instead is that whichever character has the best dicepool is considered the main acting character, and the other characters are considered the assisting characters. Each assisting character makes their check, and each hit is added as a bonus die on the main character's test. Since characters get about 1 hit per three dice, on average improving the awesomeness of a task is "hard" (threshold 3). In many cases an MC will allow a character to assist with a tangential but vaguely related skill (and in such cases it is entirely possible for one of the assisting characters to roll more dice than the main acting character).

Maximum Characters: Too many cooks spoil the broth. How many characters qualify as "too many" is unfortunately a very fluid concept that depends a lot on what you're doing. Sometimes there are real physical limits to how many people can literally fit around a project, and other times it's procedural. In general, most teamwork projects should be handled with five or less people. A project larger than that should probably be split into multiple tests, although at the MC's discretion there may be exceptions. A good set of management protocols is essential for most group projects to move forward. Most of the time, no more assisting characters can work on a project than the highest Tactics skill of the characters. The character providing the tactics skill allowing multiple characters to work on the project need not be the main acting character, and often will not be.