This is the continuation of my presentation of Charles Smith's almost 80-year old advice on running games for groups. Part 1 is here.
Expect the Best. The text describes progressive mastery of gradually harder tasks, or learning desirable tasks that are similar to the possibly undesireable behaviors that kids will engage in on their own. For applicability to simulation games, this reminds me of gradually introducing more complicated rules as players master basic rules (especially games like Advanced Squad Leader). I'm drawing a blank on the second part.
Discipline Positively. Be a "cheery suggester" rather than a "dominating director." "When problems arise our first tendency is to blame the other fellow, but if we ask ourselves first, 'Is there anything wrong with my leadership?' second, 'Is the author to blame for suggesting such a game?' and finally, 'Is anything wrong with the players?' we must admit that the players are usually doing their best. When children find pleasure in tormenting or disobeying, the leader should try to discover his own deficiencies. usually players have well founded reasons for unusual conduct or lack of cooperation. A successful leader can secure attention by merely asking for it and refusing to talk until he gets it. He makes the group feel that the individual annoying the leader is transgressing against the group rather than against the leader." There's a great big quote for GMing. This philosophy is an explicit part of leadership positions in Battlemaster.
Change Plans. Situations change, and you should have a wide enough repetoire of options that you can adapt to unforeseen circumstances. Don't railroad your players. Players will come up with all sorts of plans and actions that don't fit your preparations, and the games will be much more fun and rewarding if you can roll with them.
Provide "Re-creation," Avoid "Wreck-Creation." "The physical well-being and happiness of the people in a leader's charge should be his first consideration." Kids need rest breaks. Players need breaks too, but I've never known this to be a problem.
Develop Athletic Girls. Physical games are great for girls up to age 12 or 14, just the same as boys. Hey, role-playing games are great for girls of all ages.
Know Your People. Offer games that the kids will actually like to play (different ages have different abilities and preferences). This should be a no-brainer. You will not have much of a game if you try to run games your friends do not want to play.
Consider Outside Interests. People like variety in addition to things that they are good at. My paraphrasing of Smith's writing in this section does not really match the header, but both are good to keep in mind. Games can integrate the varied interests of your players, as well as expose them to new topics they may enjoy.
Provide for All. Avoid games in which losers drop out. Dodge Ball is a horrible game because the kids who need most to develop skills are excluded early on and sit around. For RPGs I think this translates into avoiding games in which characters can permanently die. This is controversial, and your group is probably able to decide whether they want that or not, but especially new players may not accurately predict how they would be affected by permanent character death.
Consider the Place. Don't have city kids play soccer near a forest because they will just want to play hunting/seeking/exploring types of games. This may be another non-issue. I've never known this to be a problem. Gaming groups are generally good about coming together to play the game, and not to get distracted.
Next up: 19 principles of recreation from Howard Braucher, Secretary of the National Recreation Association in the mid-1930s. Then I'll get back to the math and simulation mechanics.
I analyze, evaluate, and comment on tabletop role-playing game (RPG) mechanics. I address issues of game balance, simulation accuracy, min-maxing, and optimization.
Jun 16, 2011
Jun 13, 2011
Game Mastering: Old School Advice from Charles F. Smith part 1
I had the great fortune to come across a copy of Games and Game Leadership by Charles F. Smith (the 1949 13th ed; the first was published in 1933). Though it mostly refers to group games of physical activity for children, many of the principles apply to running table-top role-playing games (and parenting). Professor Smith taught a university course on the topic for many years. Here are some excerpts (in quotes), paraphrases, and notes (in italics) on how they may apply to modern RPG game mastering (dungeon mastering, storytelling, whathaveyou). Some of these do not apply very well, but I include them for interest.
Be Enthusiastic. Enthusiasm is contagious. Enjoy your work. An enthusiastic GM may have an easier time engaging the interests of players, and have a lower chance of burnout.
Develop a Sense of Humor. Be human and share in the fun of the tasks rather than being a dictator. If your players are engaging in a lot of humorous table talk instead of focusing seriously on the game, accept that that's what they're enjoying and roll with it.
Overlook Mistakes. Be sympathetic and understanding. "The person who makes he mistake invariably feels worse for having erred than any one else. If he blunders due to lack of skill, the leader should help him to develop the necessary skill. Every one who participates in athletics appreciates the coach who subtly points out errors in a general way rather than one who constantly finds fault with the individual members of the team." If someone gets a significant rule or mechanic wrong, you can remind the table of the rule while being considerate of the player's feelings.
Anticipate Blunders. Anticpate common blunders and check them without interrupting the game (like the rafting instructors blocking the bad routes on the river). "Individual reprimands are warranted only when the act in question threatens the moral growth of the entire group." Maybe put some bookmarks in your rulebook or photocopy frequently referenced rules or tables to help people play quickly and accurately. Scold people who seem to be bending rules on purpose.
Be Lenient. Do not nag. Let the kids have fun and not play in an exact way (but they still have to follow the rules.) Rules may be less important to follow in an RPG. Charles was mostly writing from the perspective of adults teaching games to kids.
Develop Confidence Through Preparadness. "Confidence is acquired through experience, but even the experienced leader enjoys such confidence only when he is thoroughly prepared to do the particular
work at hand.... He sees ways for improving both the game and his leadership and is able to say the right thing at the right time, in order to create either the desired moral effect or happy morale. ...the way to win respect is to be prepared, even refer to notes if necessary." Be prepared, that's the Boy Scouts' marching song....
Guard Against Overconfidence. You don't know everything. Invite suggestions as to new ways of playing old games or to draw assistants to your confidence in the making or executing of your plans. Don't pretend to be perfect, it just makes you look foolish. I have greatly enjoyed running a huge game with a couple assistants, and I have enjoyed being a player in a game in which the players' input was solicited and used. Not only is humility a great virtue, games are easier to run and more fun for the players when the GM accepts input and help.
Conquer Trying Situations. Maintain poise, striving always at least to appear at ease when vexatious situations arise. "Avoid petty squabbles." Stay calm. This is good advice all the time. Be cool.
Adopt a Positive Attitude. The descriptive text indicates that this means Be Decisive in modern English. Make the decisions instead of deferring authority to someone else. The GM makes the rules calls. The GM's word is law. I'm in favor of a One Appeal rule, but after the appeal the matter is settled. Be assertive without being aggressive. Be clear and firm. Don't let a friend or overbearing player make rules calls for you.
Lead Just Enough. "Lead just enough to set the pattern without crushing the initiative of the players." Children need experience with self-direction under supervision since they are not always supervised. Don't railroad your players.
That's enough for part 1. I've got a few more for part 2, then a follow-up post or two from another section of the book. Good stuff.
Be Enthusiastic. Enthusiasm is contagious. Enjoy your work. An enthusiastic GM may have an easier time engaging the interests of players, and have a lower chance of burnout.
Develop a Sense of Humor. Be human and share in the fun of the tasks rather than being a dictator. If your players are engaging in a lot of humorous table talk instead of focusing seriously on the game, accept that that's what they're enjoying and roll with it.
Overlook Mistakes. Be sympathetic and understanding. "The person who makes he mistake invariably feels worse for having erred than any one else. If he blunders due to lack of skill, the leader should help him to develop the necessary skill. Every one who participates in athletics appreciates the coach who subtly points out errors in a general way rather than one who constantly finds fault with the individual members of the team." If someone gets a significant rule or mechanic wrong, you can remind the table of the rule while being considerate of the player's feelings.
Anticipate Blunders. Anticpate common blunders and check them without interrupting the game (like the rafting instructors blocking the bad routes on the river). "Individual reprimands are warranted only when the act in question threatens the moral growth of the entire group." Maybe put some bookmarks in your rulebook or photocopy frequently referenced rules or tables to help people play quickly and accurately. Scold people who seem to be bending rules on purpose.
Be Lenient. Do not nag. Let the kids have fun and not play in an exact way (but they still have to follow the rules.) Rules may be less important to follow in an RPG. Charles was mostly writing from the perspective of adults teaching games to kids.
Develop Confidence Through Preparadness. "Confidence is acquired through experience, but even the experienced leader enjoys such confidence only when he is thoroughly prepared to do the particular
work at hand.... He sees ways for improving both the game and his leadership and is able to say the right thing at the right time, in order to create either the desired moral effect or happy morale. ...the way to win respect is to be prepared, even refer to notes if necessary." Be prepared, that's the Boy Scouts' marching song....
Guard Against Overconfidence. You don't know everything. Invite suggestions as to new ways of playing old games or to draw assistants to your confidence in the making or executing of your plans. Don't pretend to be perfect, it just makes you look foolish. I have greatly enjoyed running a huge game with a couple assistants, and I have enjoyed being a player in a game in which the players' input was solicited and used. Not only is humility a great virtue, games are easier to run and more fun for the players when the GM accepts input and help.
Conquer Trying Situations. Maintain poise, striving always at least to appear at ease when vexatious situations arise. "Avoid petty squabbles." Stay calm. This is good advice all the time. Be cool.
Adopt a Positive Attitude. The descriptive text indicates that this means Be Decisive in modern English. Make the decisions instead of deferring authority to someone else. The GM makes the rules calls. The GM's word is law. I'm in favor of a One Appeal rule, but after the appeal the matter is settled. Be assertive without being aggressive. Be clear and firm. Don't let a friend or overbearing player make rules calls for you.
Lead Just Enough. "Lead just enough to set the pattern without crushing the initiative of the players." Children need experience with self-direction under supervision since they are not always supervised. Don't railroad your players.
That's enough for part 1. I've got a few more for part 2, then a follow-up post or two from another section of the book. Good stuff.
Labels:
Game Mastering,
History
Jun 10, 2011
Side Note
I finally gave GURPS 4th edition a perusal, and I was really impressed. It looks like it fixes some of the bigger problems I had with 3rd edition. I am happy to see that point costs for HT and ST have been decreased to reflect their in-game utility relative to DX and IQ. Also, point costs for changing these four attributes have been made linear, which gets rid of the weird bump in 3rd ed. and looks prettier, though I will not go so far as to say a linear cost progression is necessarily the right way to go. Since probabilities of success follow a nice normal curve, we see decreasing returns on investment either way, but less severely with the linear costs.
I am also a big fan of many powers being turned into "advantages", and the wide variety of modifiers available to customize how the powers work and how much they cost. I haven't taken the system for a ride yet, but it looks good.
The main downside is how bulky it is. Well, maybe it's an upside. My impulse is to say that players should make characters by first thinking up a detailed character concept, then going through the books from the beginning writing down what that character would cost, then selecting deleting that go over the point limit for the campaign, or enhancing what's there if the limit has not been reached. There's way too much to memorize or keep in mind to make quick characters, but likewise it is far harder than other systems to game. It is less obvious how to make characters that are uniformly better than others for the same points. I'll keep poking at it over time.
Now that I've got falling deaths out of my system, I'm thinking of working on analyses and guides for strength scales or movement speeds. I've got some good numbers hanging around, but not as much time as I'd like.
I am also a big fan of many powers being turned into "advantages", and the wide variety of modifiers available to customize how the powers work and how much they cost. I haven't taken the system for a ride yet, but it looks good.
The main downside is how bulky it is. Well, maybe it's an upside. My impulse is to say that players should make characters by first thinking up a detailed character concept, then going through the books from the beginning writing down what that character would cost, then selecting deleting that go over the point limit for the campaign, or enhancing what's there if the limit has not been reached. There's way too much to memorize or keep in mind to make quick characters, but likewise it is far harder than other systems to game. It is less obvious how to make characters that are uniformly better than others for the same points. I'll keep poking at it over time.
Now that I've got falling deaths out of my system, I'm thinking of working on analyses and guides for strength scales or movement speeds. I've got some good numbers hanging around, but not as much time as I'd like.
Jun 5, 2011
Death by Falling: Revisions and Simulation
One thing I realized while looking over my last post was that I only showed chance of death by impact velocity, not by distance. Of course, you could calculate distances yourself, but I want to be more helpful than that (see second graph below). Also, I've been bothered by my assumption of how many meters tall a "floor" is. I had originally used the average height of the Empire State Building (12' per floor), but later used 3.5m. This morning I checked out a resource for average floor heights by building type, and used those numbers instead, assuming that Ramos's and Delany's data was mostly from residential buildings. Here is the revised graph of probabilities of death by impact velocity:
Here is the graph that I have put together from my estimates for chance of death for an average person by distance fallen, as well as two possible dice systems for simulation:
So, for a 3d6 system, you would try to roll higher than or equal to (meters_fallen - 9). For a 3d10 system, just roll higher than or equal to the number of meters fallen. For elderly characters, maybe add 2 to the number of meters fallen, or multiply by 1.5. For children or acrobats, maybe subtract 1 from meters fallen, or multiply meters by .8. Remember that even survivors are typically severely injured, even from falls of as little as 3m, and can require extensive medical treatment.
Here is the graph that I have put together from my estimates for chance of death for an average person by distance fallen, as well as two possible dice systems for simulation:
So, for a 3d6 system, you would try to roll higher than or equal to (meters_fallen - 9). For a 3d10 system, just roll higher than or equal to the number of meters fallen. For elderly characters, maybe add 2 to the number of meters fallen, or multiply by 1.5. For children or acrobats, maybe subtract 1 from meters fallen, or multiply meters by .8. Remember that even survivors are typically severely injured, even from falls of as little as 3m, and can require extensive medical treatment.
Labels:
Death,
Falls,
Mechanics,
Probability,
Real World
Jun 4, 2011
Death by Falling: Real World Information to Guide Mechanics Development
So I don't turn away too many readers with the length of this post, here is the executive summary:
For an average person in the real world:
My Process:
To help game designers (and for myself) with developing simulation mechanics for falling fatalities, I tried to get some real world data on fatalities and injuries from falls. My first stops, of course, were the Center for Disease Control and Prevention (CDC, because it tracks all causes of death), the National Institute of Health, and the Occupational Safety and Health Administration (OSHA, part of the Dept. of Labor). Amazingly, none of these sources made available the proportions of falls that result in fatalities or injuries by distances fallen. There was just a lot of information on the numbers of people who died from falls each year by profession, age, job, and fall context (ladder, roof, scaffold, etc...) In fact, I could only find one document via the CDC reporting a proportion of falls resulting in injuries, and it was only for Americans over the age of 65 in 2006.
I turned to regular Google searches and found a few research articles from over the last four decades with some data on fall fatalities. I also explored some information on pedestrians and unbelted drivers in front-on car collisions in case I would have to use it as a not-ideal proxy for a person hitting the ground (like the Marvel system's use of charging attack mechanics). Interestingly, the fatal car collision speeds are very close to the fatal fall speeds that I found, despite significant situational differences such as body position and impact angles. People tend to survive slightly higher speed impacts in front-on car collisions than falling.
In this graph, falling speed is estimated based on distance fallen, which was also estimated because Ramos & Delany (1986) only reported distance fallen in floors (like the Marvel system). The rest of the data points are generated by the regression equations from the Richards (2010) document, which is why the curves are so smooth.
[I later revised this graph using different assumptions about floor heights.]
Terminal Velocity:
I learned a lot about terminal velocity, and made a calculator in Excel that works for dry air. Humidity and water vapor decrease air density, but I do not know how much. For an average spread man, terminal velocity is about 56 m/s near sea level.
g = gravity (9.81 m/s at sea level)
p = air density, which equals 1.225*0.9883^(altitude_in_meters_over_sea_level/80)
a = object surface area facing down, generally .5-.6 square meters for a spread skydiver
d = drag coefficient, which is probably .6 for a person (McIlveen, 2002)
I derived the equation for air density based on other information I found, so it may not be precise. Terminal velocity is largely irrelevant because 99% fatality rates occur at about .6 of terminal velocity at sea level. Using v=at works well enough up to the nearly assured fatality point that I do not feel pressured to accurately model how drag affects falling acceleration. Wikipedia says that half of terminal V is reached in about 3 seconds, which matches v=at, but that .99 of terminal V takes 15 seconds instead of <6s. This equation relatively closely approximates velocity in m/s as a function of time (s) for a 70kg person falling near sea level: y = 0.0375 x^3 + -1.28 x^2 + 14.9x + -4.02. [Edit: I do not like how the line starts at a positive value and tilts up anti-asymptotically at the end, so I would probably replace x in the equation with (x-0.35), and say that terminal velocity is fully reached at 12 seconds.]

Facts:
Falls are one of the leading causes of injury and death, especially for kids and the elderly. Kids take less damage, and the elderly take a lot more. Falls are the 2nd leading cause of death for Americans age 60-72. About a quarter of elderly falls (from standing, steps, or furniture) result in injuries, and 1% of those result in death. 20-30% of elderly falls result in permanent debilitation.
Fatalities in the data here occur up to months after the falls. I do not have real data on instant deaths.
The average survived work-related fall results in 100 days of missed work. These falls are generally among contractors and roofers, from ladders, scaffolding, and roofs.
20-30% of fatal falls at work are not from a height! Tripping can be fatal if the head is struck against something in a bad way.
The record speed of falling is 614 mph, achieved over 40 years ago by a guy who jumped from a balloon at 30,000 meters where the air is only 0.015 as dense as it is at sea level.
Jumps from the Golden Gate Bridge, about 70m, have a 2% survival rate, but even many who survive the fall drown quickly. 80% break bones, mostly ribs, and 75% suffer lung injuries. More than half rupture their livers, and a quarter fracture their skulls. The record high dive is from about 52m (you can find videos on YouTube). It is vital to hit the water feet first, minimizing surface area and protecting the torso and head.
The Richards document for the London DfT has a great graph on injury severities by velocity.
Sources:
Center for Disease Control and Prevention. (2008). Self-Reported Falls and Fall-Related Injuries Among Persons Aged >65 Years --- United States, 2006. MMWR, 57(09), March 7, p. 225-229.
McIlveen, J. (2002). The everyday effects of wind drag on people. Weather, 57, p. 410-413.
Occupational Safety and Health Administration, Department of Labor. (2010). 29 CFR Part 1910. Federal Register 75 (99), May 24.
Ramos, S. and Delany, H. (1986). Free falls from heights: a persistent urban problem. Journal of the National Medical Association, 78 (2), p. 111-115.
Richards, D. (2010). Road Safety Web Publication No.16: Relationship between Speed and Risk of Fatal Injury: Pedestrians and Car Occupants. Department for Transport: London.
Snyder, R. and Snow, C. (1967). Fatal injuries resulting from extreme water impact. Aerospace Medicine. 38 (8).
For an average person in the real world:
- The shortest fall distance that can result in death: 0m (or I guess ~1m if we focus on center mass)
- The average distance that will result in death: ~15m
- The maximum distance a person can fall and survive: technically any with a lot of luck and medical attention, but practically closer to 30m (still with luck and medical attention)
My Process:
To help game designers (and for myself) with developing simulation mechanics for falling fatalities, I tried to get some real world data on fatalities and injuries from falls. My first stops, of course, were the Center for Disease Control and Prevention (CDC, because it tracks all causes of death), the National Institute of Health, and the Occupational Safety and Health Administration (OSHA, part of the Dept. of Labor). Amazingly, none of these sources made available the proportions of falls that result in fatalities or injuries by distances fallen. There was just a lot of information on the numbers of people who died from falls each year by profession, age, job, and fall context (ladder, roof, scaffold, etc...) In fact, I could only find one document via the CDC reporting a proportion of falls resulting in injuries, and it was only for Americans over the age of 65 in 2006.
I turned to regular Google searches and found a few research articles from over the last four decades with some data on fall fatalities. I also explored some information on pedestrians and unbelted drivers in front-on car collisions in case I would have to use it as a not-ideal proxy for a person hitting the ground (like the Marvel system's use of charging attack mechanics). Interestingly, the fatal car collision speeds are very close to the fatal fall speeds that I found, despite significant situational differences such as body position and impact angles. People tend to survive slightly higher speed impacts in front-on car collisions than falling.
In this graph, falling speed is estimated based on distance fallen, which was also estimated because Ramos & Delany (1986) only reported distance fallen in floors (like the Marvel system). The rest of the data points are generated by the regression equations from the Richards (2010) document, which is why the curves are so smooth.
[I later revised this graph using different assumptions about floor heights.]
Terminal Velocity:
I learned a lot about terminal velocity, and made a calculator in Excel that works for dry air. Humidity and water vapor decrease air density, but I do not know how much. For an average spread man, terminal velocity is about 56 m/s near sea level.
Terminal Velocity = SQRT(2mg/pad)
m = mass of object in kgg = gravity (9.81 m/s at sea level)
p = air density, which equals 1.225*0.9883^(altitude_in_meters_over_sea_level/80)
a = object surface area facing down, generally .5-.6 square meters for a spread skydiver
d = drag coefficient, which is probably .6 for a person (McIlveen, 2002)
I derived the equation for air density based on other information I found, so it may not be precise. Terminal velocity is largely irrelevant because 99% fatality rates occur at about .6 of terminal velocity at sea level. Using v=at works well enough up to the nearly assured fatality point that I do not feel pressured to accurately model how drag affects falling acceleration. Wikipedia says that half of terminal V is reached in about 3 seconds, which matches v=at, but that .99 of terminal V takes 15 seconds instead of <6s. This equation relatively closely approximates velocity in m/s as a function of time (s) for a 70kg person falling near sea level: y = 0.0375 x^3 + -1.28 x^2 + 14.9x + -4.02. [Edit: I do not like how the line starts at a positive value and tilts up anti-asymptotically at the end, so I would probably replace x in the equation with (x-0.35), and say that terminal velocity is fully reached at 12 seconds.]

Facts:
Falls are one of the leading causes of injury and death, especially for kids and the elderly. Kids take less damage, and the elderly take a lot more. Falls are the 2nd leading cause of death for Americans age 60-72. About a quarter of elderly falls (from standing, steps, or furniture) result in injuries, and 1% of those result in death. 20-30% of elderly falls result in permanent debilitation.
Fatalities in the data here occur up to months after the falls. I do not have real data on instant deaths.
The average survived work-related fall results in 100 days of missed work. These falls are generally among contractors and roofers, from ladders, scaffolding, and roofs.
20-30% of fatal falls at work are not from a height! Tripping can be fatal if the head is struck against something in a bad way.
The record speed of falling is 614 mph, achieved over 40 years ago by a guy who jumped from a balloon at 30,000 meters where the air is only 0.015 as dense as it is at sea level.
Jumps from the Golden Gate Bridge, about 70m, have a 2% survival rate, but even many who survive the fall drown quickly. 80% break bones, mostly ribs, and 75% suffer lung injuries. More than half rupture their livers, and a quarter fracture their skulls. The record high dive is from about 52m (you can find videos on YouTube). It is vital to hit the water feet first, minimizing surface area and protecting the torso and head.
The Richards document for the London DfT has a great graph on injury severities by velocity.
Sources:
Center for Disease Control and Prevention. (2008). Self-Reported Falls and Fall-Related Injuries Among Persons Aged >65 Years --- United States, 2006. MMWR, 57(09), March 7, p. 225-229.
McIlveen, J. (2002). The everyday effects of wind drag on people. Weather, 57, p. 410-413.
Occupational Safety and Health Administration, Department of Labor. (2010). 29 CFR Part 1910. Federal Register 75 (99), May 24.
Ramos, S. and Delany, H. (1986). Free falls from heights: a persistent urban problem. Journal of the National Medical Association, 78 (2), p. 111-115.
Richards, D. (2010). Road Safety Web Publication No.16: Relationship between Speed and Risk of Fatal Injury: Pedestrians and Car Occupants. Department for Transport: London.
Snyder, R. and Snow, C. (1967). Fatal injuries resulting from extreme water impact. Aerospace Medicine. 38 (8).
Labels:
Death,
Falls,
Probability,
Real World
May 25, 2011
Death by Falling
[Edit: If you're looking for real information on deaths by falls, see my next two posts here and here.]
This is the first of several posts I have planned about simulating the results of falls from elevations. Here I simply determined the minimum distance necessary to fall for an average human to die, the distance at which an average person would die on average, and the maximum distance that an average person could fall without dying for ten different systems.
As you can see, there are wide differences among systems. The grades I give are subjectively based on how each mechanic models reality and contributes to game balance.
This is the first of several posts I have planned about simulating the results of falls from elevations. Here I simply determined the minimum distance necessary to fall for an average human to die, the distance at which an average person would die on average, and the maximum distance that an average person could fall without dying for ten different systems.
As you can see, there are wide differences among systems. The grades I give are subjectively based on how each mechanic models reality and contributes to game balance.
- Aberrant: For any fall under 30 meters, even the most feeble person has a 99.6% chance of only sustaining minor injuries that will heal in a day (bashing damage). At 30 meters, damage becomes lethal and maxes out at 10 dice (an average of 4 levels of damage), with only a 1.3% chance of dying even when falling miles. F
- Chaosium: Average health is actually 12hp, not 11, but the distances are correct. 1d6 damage for each 3 meters gives us a nice distribution of injuries and chances of death up to the assured death point at 36 meters. B
- D&D 3.5 (OGL): The average human in this system has 1d4 hp, which I round up to 3, but does not die until reaching -10 hp. Most falls that are not immediately fatal will still result in wounds that may result in a person's eventual death if not stabilized, but I did not calculate that. B
- D&D 4th ed.: The most appropriate stats I found for a non-heroic person in this game were for "Human Rabble", who have 1 hp. At 1d10 damage for each 10' fallen, everybody dies from any fall of at least 10'. D
- GURPS 3rd ed.: Damage involves rolling 1d6 and subtracting a constant for each yard fallen. Since it is possible to roll the constant or less on each 1d6, it is possible to take no damage at all when falling from any height. Instant death requires 6xHealth damage in the GURPS systems. D
- GURPS 4th ed.: Now there is an equation for determining how many d6 to roll based on velocity. GURPS in one of the few systems that takes acceleration into account instead of just distance. A-
- Heavy Gear: Roll 1d6 for each meter up to 10 meters, and multiply the result by meters fallen up to 30. Remember that the Silhouette system is funky, so "result" means the highest number rolled among the dice, and additional 6s each add 1 to the first 6. It is possible (ridiculously unlikely) to roll all 1s and survive any fall. It is also possible (ridiculously unlikely) to roll all 6s and die falling 5 meters. An average person has a 40% chance of death falling 8 meters, and an 81% chance of death falling 9 meters. B-
- Marvel Super Heroes 2nd ed.: The rules as written were clearly not proofread or edited. They make absolutely no sense in the English language. On page 21 the rules say to take 1 point of damage for each floor fallen (a person would have to fall 24 floors), but also say to treat falling as a charge attack. Charge attack rules on page 27 gave me the numbers I use for this post. Using the Empire State Building for reference, I decided that a "floor" is 12 feet. F
- Rifts: People take 1 point of damage for each 10' fallen. Instant death is at -(PE+1) hp. A healthy average person will survive any fall under 390'. F
- Shadowrun 4th ed.: I did not find stats for an average human. Humans have 1-6 body points, bought up from 1 at character creation. Looking at sample characters, I figured that an average human has a body of 2. Damage from falls over 6m is about (distance+4)/2, and characters roll (Body)d6 to resist some damage. For someone with a Body of 3, the distances are 22m, 24m, 28m. C
- 7th Sea: This is a game focused on dramatic swashbuckling stories, and seems to not have rules for falls.
Labels:
Aberrant,
Chaosium,
Damage,
Death,
DnD,
Falls,
GURPS,
Health,
Heavy Gear,
Marvel,
Mechanics,
Probability,
Rifts,
Shadowrun,
Silhouette
May 9, 2011
What Systems Do I Like?
People often ask me, "Why aren't you wearing any pants?" Less often, they ask, "What is your favorite role-playing game?" That is a slightly complicated question. By which criteria do I judge RPGs? The focus of this blog is their game mechanics, but a game may be a favorite based on the quality of the setting or how much fun with friends the game creates independently of mechanics and setting. Here are the RPGs I am familiar with, and how I feel about them:
- Mutants and Masterminds: This is my favorite right now. I have been very impressed with M&M's game mechanics. It fixes nearly all of the problems I have with the d20 system (OGL 3.5). There are some opportunities to min-max and create incredible powers, but an attentive GM can easily prevent it. I love the superpower setting, but the mechanics can actually be applied to recreate most other settings. I was impressed by Green Ronin for this game, and was looking for information on the 3rd ed. at their website when I found this article by their designer of the Dragon Age TTRPG in which he agrees with my own conclusion about die rolls.
- Action!: This free system by Gold Rush Games comes with instructions on customizing it! I just stumbled upon this recently and have not played it, but it incorporates mechanics that I would use if I were creating a system. It is worth checking out.
- Aberrant: This game has some of the most broken mechanics, and the canon storyline railroads campaign plots, but I have had tons of fun playing supers in this setting with friends and watching moral and ethical dilemmas unfold.
- Vampire: the Masquerade: I LARPed (live-action role-played) this for many years with the last version of the rules and setting. I have not seen the current edition. I met a lot of people this way, though not all of them were good to meet. LARPing is a great role-playing experience, and V:tM is the easiest way to experience this because it is so widespread. It's the Dungeons & Dragons of LARP. Role-playing with 50+ people at a time is a blast, and this game fosters social and political maneuvers, shifting alliances, and secrets for a fun game. Many of the other White-Wolf LARPs (Changeling, Werewolf, Mage, Oblivion) were not as conducive. A bad storyteller will rely on sending monsters in for the player characters to fight, but good storytellers have long-term NPCs infiltrate player factions and subtly construct mysteries to be solved, complete with red-herrings and ambiguous clues that lead to both conflict and collaboration. The mechanics are not great.
- Dungeons and Dragons: This is the Microsoft of the RPG world. New gamers tend to come in with D&D because it has such a broad and deep foundation. So many people play because so many other people play, and if you want to get in on a game, it is easier to find players familiar with and owning materials for D&D. I don't like classes in games because they are too constricting, and lead to conformity instead of creativity. I don't like levels in games because they also prevent customization and realistic development. I don't like hit points in games because they are wholly unrealistic, and seem to solely exist to support the level system. D&D has classes, feats, and powers set in stone in their system so they can sell lots of books with more. What I like is the mechanics to create whatever powers are desired so that players can create whatever they want from a core book. The d20 provides a linear progression of probabilities of success. I have played each edition of D&D since the late '80s because those were the games my friends were running (and once I had the materials to play with them, I also ran a campaign), but I have not been satisfied.
- Heavy Gear: I played in one campaign about 13 years ago, and I remember it being fun, largely because of the group. The mechanics are a little weird, and encourage some min-maxing, but are relatively simple and straightforward. The setting is not totally sensible, but provides opportunities for some different styles of campaigns. You can also play a flat-out tactical mech game.
- GURPS: I only got to play GURPS once, but I've made characters in anticipation of other games I was told would happen. I like that it is generic and uses point-buys. The skill system tries well to be a good simulation, which I like, but is not great for game balance. I do not like that powers and equipment are individually determined by Steve Jackson Games instead of them also giving us a point system for creating them.
- Chaosium: I'm getting around to it.
- Shadowrun: Also, just sitting on my shelf.
- Rifts: Totally silly. Thanks, Palladium.
Labels:
Side Note
Subscribe to:
Posts (Atom)




