Do you have lucky dice? This is a slightly modified version of something I wrote a couple years ago that I think has a place here.
I have encountered more than one gamer over the years who believes that he has lucky dice. These dice are reported to roll the highest damage, the most critical hits, and generally turn the player's characters into unstoppable juggernauts. Of course, I did not notice any disproportionate numbers of good or bad rolls. I argued with these players that their perceptions were tainted by the availability heuristic and confirmation bias. When they can more easily recall rolling good numbers with certain dice, they label the dice "lucky". Then, whenever those dice roll well, they say, "See? This proves the dice are lucky!" Whenever the dice roll poorly, they say, "That was a fluke! These lucky dice usually roll well.", and fail to store the failures for future recall, feeding back into the availability heuristic. Well, there is a relatively easy way to determine if a die is lucky.
If you think you have a lucky die, record what it rolls EVERY TIME. If you believe it is lucky only in a certain situation (e.g.: "This is my saving-throw die!"), then record what it rolls every time you roll it in that situation. Do not leave out any rolls. There are no Mulligans. When you have a good amount of rolls (at least 30, but more is better), you can calculate the z-score for them, then compare that z-score to a threshold. This comparison is called a one-tailed test of proportion, and we use this specific type of comparison to test the hypothesis that your die rolls a higher (not just different) proportion of good rolls than a fair die. Though there are different ways to calculate the z-score based on how sure you want to be of the results, the following simple examples should be good enough for most of you.
The equation for z is:
z = (p - Po) / (sqrt((Po(1 - Po))/n))
The variables are:
p: the proportion of the rolls you recorded that were good (natural 20, 11 or higher, 8-10 on 1d10, etc...). p = ((# of good rolls) / (total # of rolls)).
Po: the proportion expected of fair dice (0.05 for a natural 20, 0.5 for 11 or higher on d20, 0.3 for 8-10 on d10). This should technically be written as pi subscript 0.
n: the total number of rolls you recorded
To make things easy, we will use an alpha of .05 in the examples (I explain further down). This gives us a threshold of 1.645. So, all you have to do is figure out z using the equation above (or one of the examples below), and if z > 1.645 you can claim that you may have a lucky die.
Example 1:
"My die rolls high."
Po = 0.5 (half of a fair die's rolls will be above the mean, and half below)
z = (p - 0.5) / (sqrt(0.25 / n))
Example 2:
"I roll 20s."
Po = 0.05
z = (p - 0.05) / (sqrt(0.0475 / n))
To elaborate on Example 1, let's say that I claim I have a d20 that usually rolls at least an 11, and I have countless stories of how it let my characters defeat monsters and overcome challenges. I want to prove to my naysayer friends that it really is lucky, so I write down every roll for a month. I rolled the die 100 times. 58 of the rolls were at least 11, and 42 were 10 or less. I get really excited about rubbing it in everyone's faces, but remember that there's more to do. After all, I only rolled the die 100 times, and even a fair die is likely to roll 58/100 good rolls eventually. Fair dice are only expected to roll exactly 50/50 as the number of rolls approaches infinity. So, I plug in the variables:
p = 0.58
n = 100
Po = 0.5
z = (0.58 - 0.5) / (sqrt(0.25 / 100)) = 1.600
1.600 < 1.645 (our threshold)
We should probably not be impressed that 58 of the rolls were above average. If the die had rolled 59 good rolls out of 100, z would have been 1.800. What would that mean?
This is where I need to explain about alpha. In this case, alpha is the probability that you have a fair die even if z is greater than the threshold. Usually, an alpha of 0.05 lets us feel confident enough that the effect we have observed is based on the properties of what we are observing instead of a statistical fluke of the sample of observations. It is easy to increase our confidence by using a smaller alpha, such as 0.01 (which would increase the z threshold), but using a smaller alpha increases the probability that we falsely think a lucky die is fair. There is a trade-off between the risks. Personally, I would demand a high degree of confidence, and would insist on an alpha of at most 0.01. The best way to manage both risks of false results is to get a bigger sample of rolls. So, if you want to be more sure of whether your die is lucky or not, record 200 rolls, or 500. The bigger n gets, the better.
When alpha is 0.01, the z threshold is 2.328, so even 59% good rolls does not make me confident that the die is lucky. For an alpha of 0.01, 62 out of 100 rolls would have to be above average.
To elaborate on Example 2, let's find out how many natural 20s have to be rolled with an alpha of 0.01 for someone to tell me that he rolls 20s.
(p-0.05)/(sqrt(0.0475 / 100)) > 2.328
(p-0.05)/0.0218 > 2.328
p-0.05 > .0507
p > .1007
You would have to roll 11 20s out of 100 rolls.
Good luck.
I analyze, evaluate, and comment on tabletop role-playing game (RPG) mechanics. I address issues of game balance, simulation accuracy, min-maxing, and optimization.
May 6, 2011
May 2, 2011
Graphs of Success Probability by Skill Total and Difficulty
I've given you tables of success probabilities by skill total and difficulty for two systems (World of Darkness, Shadowrun 4th ed.), plus a graph for Heavy Gear. Here I present that information again in graphs, plus two more systems, to show some of the different patterns that exist for success probabilities with increases in skill among different systems.
Linear
Here is your standard d20 system, most popular in Dungeons and Dragons. Each character has a skill modified by an attribute and various other junk, added to a d20 result and compared to a difficulty level. Each increase in the skill total raises the probability of success by 5% linearly. There is always at least a 5% chance of failure (rolling a 1). In the D&D games, skills are not bought with general character development points, but characters are alloted a few points each level to be used only for skills. Difficulty levels typically scale with character levels, so it behooves players to specialize in a few skills that are always increased with the character level in order to maintain good probabilities of success as characters level up. I am not getting in to "taking 10" or "taking 20".
Inconsistent
Here is the graph for Dream Pod 9's Silhouette system, used in their Heavy Gear game. We can see that the progression is not consistent. The lowest skill is concave, rapidly dropping the probability of success at low difficulties relative to the drop at higher difficulties where the probability of success is already very low. A skill of 1 has a linear descent. Higher skills progressively maintain high success rates among lower difficulties before rapidly plunging at higher difficulties, and then there is the bent tail as it becomes more possible to roll multiple 6s. Attribute bonuses are added to skill roll results, shifting the graph to the right without changing its shape.
Normal
Isn't that pretty? I am not sure if I am completely representing the GURPS system accurately here, but I think players just have to roll lower than the characters' skills on 3d6 to succeed at tasks (17s and 18s fail). So, there is no real "difficulty level" for tasks other than what is forced by skill levels. There may be modifiers that increase or decrease a skill for the purpose of a challenge, shifting the whole curve to the left or right. If we graphed the probabilities of each individual outcome for 3d6, the line would be shaped like a bell. I call this "normal" because as a "normal distribution" it has higher probabilities of outcomes in the middle, progressively less likely outcomes away from the middle, and is relatively symmetrical.
Inconsistent Normal
We can see here that both Shadowrun by Catalyst Game Labs and World of Darkness by White Wolf approach the normal curve as their dice pools (skill total, or skill + attribute) increase. With few dice in these systems, it is impossible to approximate the distribution of the normal pattern, and the results more follow the Inconsistent pattern. These systems both involve rolling multiple dice (d6 and d10, respectively), and counting die results over a threshold as "successes". Players need a number of successes equal to a task's difficult in order to succeed. So, the terminology can get annoying as people get a bunch of successes but still fail at a task.
I really like how the Normal distribution of probabilities of success works in simulations, but not necessarily the way that GURPS implements it in the absence of difficulty levels. In real life, when we encounter tasks far below our skill level, we are quite likely to succeed at them and have a low variance with our high success rate. When we encounter tasks far above our skill level, we are quite likely to fail at them and have a low variance with our high failure rate. Tasks closer to our skill level have increasingly variant success rates. Because of this, I am in favor of the use of normal distributions of probability of success in simulation systems. This typically requires rolling more than one die and summing the results.
Linear
Here is your standard d20 system, most popular in Dungeons and Dragons. Each character has a skill modified by an attribute and various other junk, added to a d20 result and compared to a difficulty level. Each increase in the skill total raises the probability of success by 5% linearly. There is always at least a 5% chance of failure (rolling a 1). In the D&D games, skills are not bought with general character development points, but characters are alloted a few points each level to be used only for skills. Difficulty levels typically scale with character levels, so it behooves players to specialize in a few skills that are always increased with the character level in order to maintain good probabilities of success as characters level up. I am not getting in to "taking 10" or "taking 20".
Inconsistent
Here is the graph for Dream Pod 9's Silhouette system, used in their Heavy Gear game. We can see that the progression is not consistent. The lowest skill is concave, rapidly dropping the probability of success at low difficulties relative to the drop at higher difficulties where the probability of success is already very low. A skill of 1 has a linear descent. Higher skills progressively maintain high success rates among lower difficulties before rapidly plunging at higher difficulties, and then there is the bent tail as it becomes more possible to roll multiple 6s. Attribute bonuses are added to skill roll results, shifting the graph to the right without changing its shape.
Normal
Isn't that pretty? I am not sure if I am completely representing the GURPS system accurately here, but I think players just have to roll lower than the characters' skills on 3d6 to succeed at tasks (17s and 18s fail). So, there is no real "difficulty level" for tasks other than what is forced by skill levels. There may be modifiers that increase or decrease a skill for the purpose of a challenge, shifting the whole curve to the left or right. If we graphed the probabilities of each individual outcome for 3d6, the line would be shaped like a bell. I call this "normal" because as a "normal distribution" it has higher probabilities of outcomes in the middle, progressively less likely outcomes away from the middle, and is relatively symmetrical.
Inconsistent Normal
We can see here that both Shadowrun by Catalyst Game Labs and World of Darkness by White Wolf approach the normal curve as their dice pools (skill total, or skill + attribute) increase. With few dice in these systems, it is impossible to approximate the distribution of the normal pattern, and the results more follow the Inconsistent pattern. These systems both involve rolling multiple dice (d6 and d10, respectively), and counting die results over a threshold as "successes". Players need a number of successes equal to a task's difficult in order to succeed. So, the terminology can get annoying as people get a bunch of successes but still fail at a task.
I really like how the Normal distribution of probabilities of success works in simulations, but not necessarily the way that GURPS implements it in the absence of difficulty levels. In real life, when we encounter tasks far below our skill level, we are quite likely to succeed at them and have a low variance with our high success rate. When we encounter tasks far above our skill level, we are quite likely to fail at them and have a low variance with our high failure rate. Tasks closer to our skill level have increasingly variant success rates. Because of this, I am in favor of the use of normal distributions of probability of success in simulation systems. This typically requires rolling more than one die and summing the results.
Labels:
d20,
Distribution,
DnD,
DP9,
Dream Pod 9,
Heavy Gear,
Mechanics,
Probability,
Shadowrun,
Silhouette,
System,
Taxonomy,
White Wolf,
WoD,
World of Darkness,
WW
Apr 23, 2011
White Wolf's World of Darkness Probability Tables
White Wolf's game mechanics typically look as though they were created by coked-up baboons. I experienced a lot of frustration creating the probability tables for their 2004 version of the World of Darkness because of the mechanic of re-rolling 10s. The whole game is like rolling damage for the arquebus in old D&D. Technically, it is possible to roll forever, so I set some limits. I stop calculating when the probability of an outcome drops below 0.001, or after the third roll. It was relatively easy to find the probabilities of up to three successes with one die, then much more complicated for two dice, then after some struggles I noticed a pattern in how many separate equations must be solved and combined for each possible outcome (that meets my criteria) for a given number of dice:
So, instead of trying to solve over two thousand equations or trying to figure out how to write a computer program that would do it for me, I brute forced the problem. I used Excel to whip up 10,000 sets of 3 rolls, then mixed them up twenty different ways, then averaged the occurrences of each number of successes. The values in the following tables should be correct to about +/- 0.002. (Click on the pictures to see bigger versions. I'm annoyed with blogspot's layouts.)
And, of course, by adding from the right we can find the probabilities of rolling at least any specific number of successes. Remember that these probabilities include up to two re-rolls of 10s.
I hope that these tables will be useful to game masters (storytellers) in determining difficulty levels of challenges for characters in their campaigns. They may also be helpful to players in deciding how much to increase a skill or attribute.
So, instead of trying to solve over two thousand equations or trying to figure out how to write a computer program that would do it for me, I brute forced the problem. I used Excel to whip up 10,000 sets of 3 rolls, then mixed them up twenty different ways, then averaged the occurrences of each number of successes. The values in the following tables should be correct to about +/- 0.002. (Click on the pictures to see bigger versions. I'm annoyed with blogspot's layouts.)
And, of course, by adding from the right we can find the probabilities of rolling at least any specific number of successes. Remember that these probabilities include up to two re-rolls of 10s.
I hope that these tables will be useful to game masters (storytellers) in determining difficulty levels of challenges for characters in their campaigns. They may also be helpful to players in deciding how much to increase a skill or attribute.
Labels:
Mechanics,
Probability,
System,
White Wolf,
WoD,
World of Darkness,
WW
Apr 9, 2011
Shadowrun 4th Edition Probability Tables
This is a straightforward post of dice tables for 4th edition Shadowrun. A player rolls a number of d6s equal to the sum of the character's relevant attribute and skill. Dice that come up 5 or 6 count as successes. If at least half of the dice come up 1, a Glitch occurs (something bad) even if there are also successes. A Glitch with no successes is a Critical Glitch (something very bad). These tables assume that players do not spend edge. The first table shows the probability of each outcome for up to 15 dice.
What I find particularly interesting here is that the likelihood of both types of Glitch actually increases from 1 die to 2 dice, and that pattern continues for each even number of dice. There is a kind of mechanical penalty for being better at a task half of the time, though probabilities of successes always increases. This bizarre feature of the Glitch system does not make any sense from a simulation or game balance perspective.
This table may help game masters determine task difficulties based on characters' dice totals and the probabilities of success the GM wants in each situation.
What I find particularly interesting here is that the likelihood of both types of Glitch actually increases from 1 die to 2 dice, and that pattern continues for each even number of dice. There is a kind of mechanical penalty for being better at a task half of the time, though probabilities of successes always increases. This bizarre feature of the Glitch system does not make any sense from a simulation or game balance perspective.
This table may help game masters determine task difficulties based on characters' dice totals and the probabilities of success the GM wants in each situation.
Labels:
Mechanics,
Probability,
Shadowrun,
System
Mar 29, 2011
Dream Pod 9's Silhouette System part 2
When we last left our intrepid system, I had graphed probabilities of success at various difficulty thresholds for different skill levels, holding attributes constant, and I made the claim that the system encourages min-maxing. Let us follow up on that.
This table shows the probabilities of succeeding at tasks with a difficulty threshold of 6, which is hard, for various combinations of skill and attribute. It also shows the character creation point cost of each skill/attribute combination, and the point cost per percentage change of success.
We see that costs mirror each other across the center diagonal, and it is a more efficient use of points to buy a high attribute than a high skill. Even more important to note is that Attributes are applicable to many skills, and are sometimes used to determine secondary traits (Health is the average of Fitness, Psyche, and Willpower). So, not only would it be more efficient to buy a high attribute for just one skill, there is compound efficiency for buying a high attribute in general and with multiple related skills.
This table shows the average probabilities of success across tasks with difficulty thresholds from 1 to 7. That should be a relatively standard distribution, since a threshold of 4 is considered average.
A notable difference here is that it is actually more efficient in some cases to buy a lower attribute than skill, but only when the average probability of success is less than 51%, which is not usually desirable in a heroic simulation. At the useful levels of success, it is still more efficient to buy a high attribute, even for a single related skill. We also see that an attribute of 2 and a skill of 3 is a kind of sweet spot for good success at a moderate price.
There are many available skills, but the overwhelming majority of them are based on just three attributes: Agility, Knowledge, and Creativity. As far as skills go, this means there is a strong incentive to min-max, and just pick one of the three areas to focus on while taking negative scores in the other two. If you don't care about having a lot of skills, and want more of a brute character, scrap all three and raise the Build, Fitness, Psyche, and Willpower attributes instead.
Since those three attributes apply to so many skills, it would be more appropriate to make a new version of each of the above tables for each number of desired skills, adding in only the average attribute cost per skill. I am not currently inclined to make a dozen more tables. This would make it drastically more evident that a high attribute score (a 4 is possible for a starting heroic character, but a 3 is practically as high as even a min-maxer should go) allows for the most success at multiple skills for an efficient price.
Something that I did not highlight is the fact that the same point pool is not used to buy attributes and skills. It is impossible to use a huge number of points on attributes and then buy a bunch of low level skills as it is in GURPS. This system guarantees a set block of points for skills. If you don't want a lot of skills, use your attribute points to build a brute, and buy high levels of the couple skills you do want. If you want a lot of skills, pick one of the three polyskill attributes to focus on, crank it up and buy many low level related skills. I am glad that Dream Pod 9 split the pools this way, as it does slightly limit min-maxing and forces characters to have skills, but the system still does encourage attribute min-maxing within its point pool.
Also interesting is that it is incredibly difficult to increase attributes during play. The experience point costs are different than the character creation point costs, and strongly incentivize buying skills during play instead of saving up to increase an attribute.
This table shows the probabilities of succeeding at tasks with a difficulty threshold of 6, which is hard, for various combinations of skill and attribute. It also shows the character creation point cost of each skill/attribute combination, and the point cost per percentage change of success.
We see that costs mirror each other across the center diagonal, and it is a more efficient use of points to buy a high attribute than a high skill. Even more important to note is that Attributes are applicable to many skills, and are sometimes used to determine secondary traits (Health is the average of Fitness, Psyche, and Willpower). So, not only would it be more efficient to buy a high attribute for just one skill, there is compound efficiency for buying a high attribute in general and with multiple related skills.
This table shows the average probabilities of success across tasks with difficulty thresholds from 1 to 7. That should be a relatively standard distribution, since a threshold of 4 is considered average.
A notable difference here is that it is actually more efficient in some cases to buy a lower attribute than skill, but only when the average probability of success is less than 51%, which is not usually desirable in a heroic simulation. At the useful levels of success, it is still more efficient to buy a high attribute, even for a single related skill. We also see that an attribute of 2 and a skill of 3 is a kind of sweet spot for good success at a moderate price.
There are many available skills, but the overwhelming majority of them are based on just three attributes: Agility, Knowledge, and Creativity. As far as skills go, this means there is a strong incentive to min-max, and just pick one of the three areas to focus on while taking negative scores in the other two. If you don't care about having a lot of skills, and want more of a brute character, scrap all three and raise the Build, Fitness, Psyche, and Willpower attributes instead.
Since those three attributes apply to so many skills, it would be more appropriate to make a new version of each of the above tables for each number of desired skills, adding in only the average attribute cost per skill. I am not currently inclined to make a dozen more tables. This would make it drastically more evident that a high attribute score (a 4 is possible for a starting heroic character, but a 3 is practically as high as even a min-maxer should go) allows for the most success at multiple skills for an efficient price.
Something that I did not highlight is the fact that the same point pool is not used to buy attributes and skills. It is impossible to use a huge number of points on attributes and then buy a bunch of low level skills as it is in GURPS. This system guarantees a set block of points for skills. If you don't want a lot of skills, use your attribute points to build a brute, and buy high levels of the couple skills you do want. If you want a lot of skills, pick one of the three polyskill attributes to focus on, crank it up and buy many low level related skills. I am glad that Dream Pod 9 split the pools this way, as it does slightly limit min-maxing and forces characters to have skills, but the system still does encourage attribute min-maxing within its point pool.
Also interesting is that it is incredibly difficult to increase attributes during play. The experience point costs are different than the character creation point costs, and strongly incentivize buying skills during play instead of saving up to increase an attribute.
Labels:
Attributes,
DP9,
Dream Pod 9,
Min-max,
Optimization,
Probability,
Silhouette,
Skills,
System
Mar 21, 2011
RPG Mechanics Taxonomy: Probability Scales
It's taking me longer than I wanted to finish some analyses of Dream Pod 9's Silhouette system, so part 2 will be delayed while I tell you a bit about role-playing game mechanics taxonomy.
Humans love to find patterns and name things. Our brains do it automatically, giving us ways to predict the outcomes of novel situations by comparing features to those of situations we have been in in the past, though not always accurately, often resulting in bad stereotypes and superstitious beliefs. When we are mindful, we can harness this wonderful ability to organize information to facilitate analyses, searches, and predictions. We give names to groups of items that share patterns of features.
Dr. Wayne Saunders of the Museum of Man developed a taxonomy of games that identifies 20 types of game based on how they are played, and three categories of games based on victory criteria. He classifies role-playing games as "production" games because the goal is to create something rather than to win. Within RPGs, I further break down games into categories based on patterns in their mechanics.
In this post, I am going to focus on scales of probabilities that characters succeed at tasks they attempt as they relate to character creation or experience point costs. There are other mechanics that I will address in later posts. There are two main categories of probability scale features: the method by which the scales are determined, and the patterns of increases in probabilities of success as they depend on point costs. I will abbreviate these to Method and RoI (Return on Investment).
There are four Methods:
- Utility: The point costs of probabilities of success at tasks are intended to reflect how useful the tasks are in the game. Tasks that occur frequently in the game would generally cost more points for a given success probability than for less common tasks. In a typical RPG, Karate comes up a whole lot more often than Basketball, and would cost more points to be good at even though training in those skills may take similar effort in real life.
- Realism: The point costs of probabilities of success at tasks are intended to reflect how much effort it would take in the realm world to achieve such a success probability. Being an expert historian of spoons would cost the same points as being an expert computer programmer, even though one is clearly more useful (I won't tell you which one).
- Constancy: The point costs of probabilities of success at tasks are all the same, regardless of task utility in-game or the effort required to learn how to accomplish the tasks in real life.
- Arbitrary: The game creators just assigned costs to success probabilities without strictly or clearly using one of the other three methods.
- Increasing: The increase in probability of success increases with additional point expenditures.
- Decreasing: The increase in probability of success decreases with additional point expenditures.
- Equal: The increase in probability of success is the same for every point expenditure.
- Inconsistent: The increase in probability of success is sometimes higher or lower or equal for successive point expenditures.
How would you classify your favorite system?
Mar 7, 2011
Dream Pod 9's Silhouette System part 1
I had a lot of fun playing Heavy Gear by Dream Pod 9 with friends back in undergrad. DP9 came up with a game system it calls Silhouette. I remember a friend telling me that it was mathematically optimized for 8-sided dice, but they just changed the dice to 6-siders because people tend to have d6s lying around. Whether or not that is true, there is a little funkiness in the system. Here is a brief intro to the dice system, and I will have a deeper report later.
In this system, characters have attributes and skills. To perform a task, the player rolls a number of d6s equal to his character's skill level (if the skill is 0, 2 dice are rolled and the lower result is used), and the highest result is used, with any 6s over the first adding 1 to the result. Then the appropriate attribute is added to the die result. So, a player whose character has an attribute of 2 and a skill of 3 will roll 3d6, take the highest die result (+1 for each 6 over the first) and add 2. The total is then compared to a difficulty threshold, and the character succeeds if the result is higher than the difficulty. If the total equals the difficulty, there is a draw, which usually favors a defender, and I am counting as a failure. If all 1s are rolled, there is a "fumble" and something bad happens regardless of modifiers.
Attribute scores effectively take away from a task's difficulty (or add to it if the attribute is negative, which is common; 0 is average for an attribute). A difficulty of 4 is supposed to be average, 8 very difficult, and 10 or more practically unattainable. Even the game creators describe the progression of success as "peculiar."
Just a cursory glance shows us that attempting tasks with a skill of 0 significantly risks fumbles, that there are diminishing returns as skills increase (I'll go more into that in part 2), and that you shouldn't count on rolling more than one 6. Also, you can see how important attributes are, shifting the entire graph to the left or right.
We had a sniper in our party with a dexterity of 3, which is a very high attribute. He was ridiculously successful at dexterity tasks for which he had little or no skill, such as piloting a Gear. This system cries out for min-maxing, and game masters should be ready to impose limits and say the magic word: "no."
In this system, characters have attributes and skills. To perform a task, the player rolls a number of d6s equal to his character's skill level (if the skill is 0, 2 dice are rolled and the lower result is used), and the highest result is used, with any 6s over the first adding 1 to the result. Then the appropriate attribute is added to the die result. So, a player whose character has an attribute of 2 and a skill of 3 will roll 3d6, take the highest die result (+1 for each 6 over the first) and add 2. The total is then compared to a difficulty threshold, and the character succeeds if the result is higher than the difficulty. If the total equals the difficulty, there is a draw, which usually favors a defender, and I am counting as a failure. If all 1s are rolled, there is a "fumble" and something bad happens regardless of modifiers.
Attribute scores effectively take away from a task's difficulty (or add to it if the attribute is negative, which is common; 0 is average for an attribute). A difficulty of 4 is supposed to be average, 8 very difficult, and 10 or more practically unattainable. Even the game creators describe the progression of success as "peculiar."
Just a cursory glance shows us that attempting tasks with a skill of 0 significantly risks fumbles, that there are diminishing returns as skills increase (I'll go more into that in part 2), and that you shouldn't count on rolling more than one 6. Also, you can see how important attributes are, shifting the entire graph to the left or right.
We had a sniper in our party with a dexterity of 3, which is a very high attribute. He was ridiculously successful at dexterity tasks for which he had little or no skill, such as piloting a Gear. This system cries out for min-maxing, and game masters should be ready to impose limits and say the magic word: "no."
Labels:
Attributes,
DP9,
Dream Pod 9,
Mechanics,
Silhouette,
Skills,
System
Subscribe to:
Posts (Atom)














