The Forge Forums Readonly Archives
The live Forge Forums

Articles

Reviews
Welcome,
Guest
. Please
login
or
register
.
July 25, 2014, 03:03:24 PM
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
Forum changes:
Editing of posts has been turned off until further notice.
Search:
Advanced search
275647
Posts in
27717
Topics by
4283
Members Latest Member:

otto
Most online today:
81
 most online ever:
429
(November 03, 2007, 04:35:43 AM)
The Forge Archives
Archive
Indie Game Design
(Moderator:
Ron Edwards
)
Algorithms, complexity and what any of this has to do with R
Pages:
1
[
2
]
3
« previous
next »
Author
Topic: Algorithms, complexity and what any of this has to do with R (Read 6115 times)
Clay
Member
Posts: 550
Algorithms, complexity and what any of this has to do with R
«
Reply #15 on:
June 15, 2001, 07:14:00 AM »
For the Philosophy majors in the audience, here's a solution that solves the same problem, but doesn't involve the rather unpleasant mathematics described here.
Try your system out on people who have never used it before. See how long it takes. If it takes too long for your target audience, simplify. If you want to know where to attack it, time each portion of the resolution and start working on the slowest one; alternatively, start working on the one that adds the least value to the game.
For instance, if I were trying to simplify Deadlands, I'd drop the whole hitlocations things completely. It adds a roll and a lookup to get a result that could have been achieved just as effectively without the additional role or lookup (e.g. count raises towards damage bonus, as in Sorcerer). Of course, I'm looking at it from a narrativist viewpoint, not a simulationist. The simulationist may see value in the existing way of doing it.
This highly empirical technique will irritate the theoretical physicists in the audience and at least a few of the mathematicians. The manufacturing engineers among you will love it. It's only true merit is that it works, without breaking your head with the math if math isn't your thing.
Logged
Clay Dowling
RPGCampaign.com
 Online Campaign Planning and Management
Zak Arntson
Member
Posts: 839
Algorithms, complexity and what any of this has to do with R
«
Reply #16 on:
June 15, 2001, 07:58:00 AM »
Quote
On 20010615 11:14, Clay wrote:
For the Philosophy majors in the audience, here's a solution that solves the same problem, but doesn't involve the rather unpleasant mathematics described here.
You rule! Hah! But yeah, I would agree that playtesting is a way better tool than math for figuring out the funfactor of a game.
I see the complexity issue coming up during initial mechanics design,
before
playtesting. Or if the playtest runs badly and you can't figure out just what is messing things up.
It certainly isn't a replacement for playtesting, more of another tool (like G/N/S) for design.
Logged
Zak
HarlekinMaus Games
greyorm
Member
Posts: 2233
My name is Raven.
Algorithms, complexity and what any of this has to do with R
«
Reply #17 on:
June 15, 2001, 08:00:00 AM »
Quote
Thanks guys, I was aiming for people with computer science background
Hey, now, I've been in programming and technical repairs for the last three years and in all that time I've never once even needed to glance at anything vaguely algorithmic.
Heck, the last time I recall them being mentioned was when our chemistry teacher went on a physics tangent during High School.
I don't even recall the subject being broached in my college Physics or Math courses (then again, I've been piss poor at math for years, so I never moved much beyond basic Algebra except as it related directly to physical theory).
I guess I just wanted to point out all us techheads aren't math geeks, too. [grin]
Logged
Rev. Ravenscrye Grey Daegmorgan
Wild Hunt Studio
Supplanter
Member
Posts: 258
Algorithms, complexity and what any of this has to do with R
«
Reply #18 on:
June 15, 2001, 08:17:00 AM »
I've been messing with a dieroll idea that seemed, intuitively, to be pretty fast, and to produce a bell curve without any addition: Roll 3 dice and take the median. Since it's a compare, it seems faster than an add. I've grown to like opposed rolls, so I'd have each side doing this.
Where one goes from there brings up more serious design questions: e.g. where character traits come into the picture, what you do with the opposed rolls etc. I've been intrigued lately by the idea of results with dimensionality and, in combat specifically, flow. I've thought about determining success purely with the "attacker's" roll, while determining advantage shifts (initiative) purely with the "defender's." IOW, the side with the advantage is pressing and the side being pressed wants to turn the tables.
Say the "combat" is basketball. One side is making a run  they are in the "attacker" position. Their roll determines the level of success of their run. The other side is trying to weather the storm  they are in the defender position. Their roll determines a possible reversal of the flow of events  a high roll for the defender represents the timely threepoint bucket or blocked shot that ends the "attacker's" run and shifts momentum to the former defender's side. As of the next roll, attacker and defender are reversed.
Anyway, since the emphasis is on flow and speed, fast dicehandling seems to be called for. Thoughts?
Best,
Jim
Logged
Unqualified Offerings
 Looking Sideways at Your World
20' x 20' Room
 Because Roleplaying Games Are Interesting
Ron Edwards
Global Moderator
Member
Posts: 16490
Algorithms, complexity and what any of this has to do with R
«
Reply #19 on:
June 15, 2001, 08:34:00 AM »
Hey Jim,
"Pick a die" from a rolled set of several dice is an excellent method. I've only seen "highest die" methods so far  Sorcerer, Orkworld, Deadlands, and the Dream Pod 9 system.
Just to clarify, in what you propose, you mean that rolling a 4, a 2, and a 1 gets you a "2," right?
I'm not sure the "median" method does much to change the general goal, as opposed to "highest die." Also, I'm puzzled about withinthethree ties. How would you handle a roll like 4, 4, and 2?
Now for my other thought: target values vs. opposed rolls.
This is a curse and a blight that has afflicted roleplayin games for decades. If my attack is a "task," and his defense is a "task," then many systems come up with highly epicyclical methods of comparing my success at my task with his success at his task. You get systems like Cyberpunk and Vampire and D6, all of which have outrageous handling times.
Anyway, as you know, Sorcerer and Over the Edge and Prince Valiant (etc) all use opposed rolls in resolving CONFLICT rather than tasks. This puts us in the tricky situation of "I win" or "he wins" without any "both succeed" or "both fail" to round out the plausible possibilities. (I think I solved this for Sorcerer by coopting Zero's roundresolution.) Hero Wars represents yet another eversoslightly clunky attempt to cope.
But now for the utterly obvious yet so underutilized option, employing target numbers. How about if the player is always ROLLING OFFENSE vs. the opponent's DEFENSE SCORE, and always ROLLING DEFENSE vs. the opponents OFFENSE SCORE? No rolling for the GM at all. This is what you're proposing, right?
This is what The Whispering Vault does, and you know, it's the ONLY version of targetnumber mechanics that I have found to be sensible/plausible and fast. And for the life of me, I don't think it LOSES any nuance of the more clunky versions of targetnumber resolution.
Just to clarify: In WV, I have an Attack of +5, so I roll and add my 5. Maybe I get a total of 13. Well, this opponent's Defense is 11, so I whopped it. When its turn to whop me back comes up, the GM doesn't roll  I roll my dice, adding my Defense of +4, maybe for a total of 9. Well, shit, its Attack is a 14, so it whopped me.
So each opponent has Attack and Defense target numbers that I use for my Defense and Attack rolls, respectively, at the appropriate moments during combat.
I think expanding this brilliant and wonderful concept to social and other instances of RPG conflict is long, long overdue. Mike Nystul gets the credit for WV, that smart fellow.
Best,
Ron
Logged
Don Lag
Member
Posts: 72
Algorithms, complexity and what any of this has to do with R
«
Reply #20 on:
June 15, 2001, 09:58:00 AM »
Logged
Don Lag
Member
Posts: 72
Algorithms, complexity and what any of this has to do with R
«
Reply #21 on:
June 15, 2001, 11:01:00 AM »
Ok, so I'm compulsive about this shit...
I built the probability distribution for the median rolling mechanism. The value frequencies (the probability of obtaining a roll equal to X) aren't a bell, but rather an inverted parabola (Ax
^{2}
+ Bx + C = D ), kinda looks like a bell but not quite, it's steeper at the extremes.
The probability for beating a difficulty of X is almost linear, in fact it doesn't change much (less than 10% discrepancy all the way) than that of rolling 1d20 (D&D style) and checking that it's higher than the diff.
If anyobody is actually interested in this I'd be glad to send them the excel sheet I worked on, just email me.
Also, if you have any questions regarding prob. distributions of some game system or whatnot, just let me know.
Logged
Supplanter
Member
Posts: 258
Algorithms, complexity and what any of this has to do with R
«
Reply #22 on:
June 15, 2001, 12:02:00 PM »
Hi Ron, thanks for the message. On a roll of 442, 4 is the median. That's how, using d6s, you can get ranges resulting from 16. (Excel will be happy to confirm my definition of median for you  just put 4,4 and 2 in three cells and run Median() on those cells et voila.)
I think you've made Sorc the fastest dice pool mechanic possible, even faster than OTE, which, I would argue, is Sorc's mechanical father.
Couple of things got me thinking this way: Fading Suns and Hero Wars, both of which use single d20s. The contrast is that in Hero Wars, masteries in your best traits give a bias toward success on checks, except against extraordinary opposition. In Fading Suns the bias is toward failure.
I prefer biases toward success when dice are used, a la HW's bumps. Failure then comes from, as you put it, conflict or opposition. (Or the rare bad roll.)
Many many years ago we spent a lot of time seeking cultural explanations for violence in RPGs, but I always thought there was a simple mechanical one as well. Consider Runquest: You might have a Persuade roll of 55%. What's more, per the rules you got to use it once per encounter. An unmodified 45% chance of failure is substantial  it implies that, if all of Glorantha is really
playing Runequest,
that that world is full of thoroughly disagreeable people.
In that same game I might also have a Broadsword roll of 55%. But if I miss with the broadsword, I get to try again! Being 55% with broadsword is far more efficacious than being 55% with persuasion. And all those failed persuasion rolls are opportunities for, oh yeah, violence!
Then there is the problem of players feeling their progress stymied by a series of failed nonviolent action checks  the persuade don't work, the interrogate don't work, the pick locks don't work, nor the library roll neither. Let's just go kill their ass!
Bond, which was one of the first great dramatist game designs, IMHO, is the first game I remember to substantially bias toward success, with its Quality Result system. Alas, the designer made the handling time longer than it needed to be by requiring two multiplication operations and then a compare for most rolls. Instead of your interrogate failing outright, you were more likely to get a Q4 result and have it take 4 times as long as it might otherwise take to get the information you wanted, etc. Plus the Expertise rules were the first I recall that allowed players to generate fiat successes in at least some areas of a game.
Which is somehow wandering afield of median rolls per se, but it's tied in there somewhere. I think because, when one goes to opposed rolls and comparing successes, one can have routine competence (which is how HW describes the first level of mastery), which is good for moving action forward, balanced with failure against worthy opposition.
One way to "correct" FS in the direction of bias toward success is to simply roll a single d10 instead of a d20 but keep the score tallies the same. That means that the target number will frequently be higher than the maximum number of pips on the die. (In FS, you want to roll under the target number but close to it.) Hero Wars suggests what to do with those "extra" points in the target roll  turn them into automatic successes. So if your Seduce target is 14 on a d10, you get 4 successes automatically, plus the value of your roll  analogous to HW bumps. Now add an opposition roll where the opposition may also have extra points too.
Best,
Jim
Logged
Unqualified Offerings
 Looking Sideways at Your World
20' x 20' Room
 Because Roleplaying Games Are Interesting
Ron Edwards
Global Moderator
Member
Posts: 16490
Algorithms, complexity and what any of this has to do with R
«
Reply #23 on:
June 15, 2001, 12:52:00 PM »
Hi Jim,
I'm with you on the "bias toward success" issue, and I'll tag first TFT, and then Champions, as the games which acted as my Sweet Relief from the everfrustrating whiff factor.
I believe it was the late70s Murphy's Rules that mocked RuneQuest's outcome in which two averageintelligent speakers of the same language, in casual conversation, had something like a 40% chance of completely misunderstanding one another. That's a lot of "Huh?" and "What?" around the dinner table.
It all becomes more sensible to me if we conceptually turn our attention toward conflict resolution as opposed to task resolution. That's one reason why either roll vs. roll (without target numbers) or that offense/defense target system from The Whispering Vault seem like the two best Fortunebased resolvers to me.
I did want to point out that Hero Wars does a very nice job of letting Very Competent People (when the task is pretty basic) sometimes have A Really Hard Time (when opposed by someone in the same ballpark of competence). If its mastery system was combined with a WVstyle target number system ... boy, that might really be something.
Hey, I just realized, for an AmberWay Drama dude, you're pretty hot with this dice talk.
Best,
Ron
Logged
Epoch
Member
Posts: 201
Algorithms, complexity and what any of this has to do with R
«
Reply #24 on:
June 15, 2001, 01:23:00 PM »
Hey, the medianofthreedice thing is unbelievably cool!
It's got all
sorts
of wonderful possibilities. For example:
Builtin tiebreaking: If two people have the same score, then look at their highdie. The higher one wins. If their high dice are also the same, look at the lowdie.
Color code the dice and use them to "flavor" the results (this one's courtesy of Justin Bacon, from whom I stole the idea). So, if you've got a red die, a green die, and a blue die, then the red die can imply a more skill or finessebased solution (or failure to resolve, as the case may be), the blue die can be brute force or stubbornness, and the green die can be lucky breaks (flavor to fit).
Critical successes or failures  if two or three dice come up the same, then the result is a higher order of magnitude.
Plus, and this is one of my own little hobbyhorses, you can code information into the die roll that the rollers don't necessarily see. So, for my theoretical "hidden magic" system, suppose you had a "roll under" system, with a target number you were trying to roll less than, a la BESM. You're rolling 3d10. Suppose the TN is 6. If you roll a 1, 3, 6, then you succeed with a roll of 3. But the GM also glances over and notes that your high die
also
succeeds and decides that you've tapped into some minor magical blessing that goes along with your skill use.
Logged
Gordon C. Landis
Member
Posts: 1024
I am CustomBuilt Games
Algorithms, complexity and what any of this has to do with R
«
Reply #25 on:
June 15, 2001, 01:26:00 PM »
In the arena of being compulsive about this shit . . .
Some months back Jared was looking for some statistical info regarding rolling "sets" on various numbers of d6 . E.g., if I roll 5d6, what's the chance I get 2 of a kind? 3 of a kind? People did some clever analysis and I'm pretty sure they gave him what he needed.
I, on the other hand, now have on my SQL Server tables containing every possible combination of values on up to 9 d6 (something over 64 million, if I remember right), and have continued to work on queries to tell me the chances for all the permutations  what's the chance of a pair, a triple, and a quad on 9 dice? What about three pair and a triple?
As I moved past 7 dice, the number of such combiniations got kinda outta control, and my analysis has taken a very deep back burner in the face of real work (I actually was doing some performance analsis where looking for an optimal way to build the huge table of all possibilities was relevant to work . . . the analysis, alas, is not). If I simplified to where all I cared about was "at least 2 pair" or "at least a pair and a triple", my life would be much simpler  but I'm committed to that full analysis, damnit! When I'm done, I will have THE definitive answer to all questions about d6 dice pools. Wouldn't be too hard to expand to other d's, as well . . .
Very sad. Especially since I'm not really a big fan of dice pool systems of ANY stripe!
Gordon C. Landis
Logged
www.snapgame.com
(under construction)
Supplanter
Member
Posts: 258
Algorithms, complexity and what any of this has to do with R
«
Reply #26 on:
June 15, 2001, 01:43:00 PM »
Hey, I just realized, for an AmberWay Drama dude, you're pretty hot with this dice talk.
Heh. It's funny. I spend all my time playing diceless games  I haven't rolled a die in an RPG since coming back to gaming about four years ago, unless you count a single session of Pantheon, which I emphatically do not. Heck, the games on my "experiment list" are Nobilis, Puppetland, Epiphany, Swashbuckler and &Sword, and you can see that that's a total of two diced games that I mean to get
around
to playing.
But then I spend all my time thinking about mechanics. Frex, suppose you had a true "d20 system" where your attack roll also determined the damage you did. (Or a d10 system, whatever.) Against an unarmored opponent, your range of results runs from clean whiff through glancing blow to whatever you decide is Maximum Damage. Now stick armor on the target. The range is really the same  clean whiff through the same Maximum Damage (You're dead, I tell you! Dead! Dead! Dead!) It's just that the result skews to the harmless end of the range. But many armor rules reduce the Maximum result, taking away the possibility of the clean, wellplaced shot. The Loose Ends crowd was musing on this issue for a possible computerized resolution system. Okay, says I, here's what you do. For a certain grade of armor  call it Light, or maybe Medium  the attacker rolls two dice instead of one, and takes the worse result. The resulting range of values is the same, but biased toward no or minimal damage. For Heavy armor, roll 3 and take the worst.
It's clear that adding dice skews "downward" very quickly, and it's not a system that differentiates scale mail from banded chain from boiled resinite or what have you, and we never really did anything with the idea. But it provides at least a "Conanlevel" of detail pretty cleanly.
For my alternate Sorcerer dice mechanic, I did consider a rolltwotaketheworst system of opposed rolls though.
Also, you have played Hero Wars a lot and I not at all, so you are far more competent to say how the mechanic works, but the impression I got was that, while Masteryvs.Mastery rolls drop you right back to failurebias in a lot of cases, the victory level table corrects you back to some level of relative success for one side or the other. Nevertheless, I think I mentioned on the GO HW forum some time ago, that with the opposing values suggested for natural phenomena (cliffs, waterslides, etc.) that they tended to put the masterful character right back in extremely chancy circumstances and the character whose score falls short of mastery in even worse shape. Your sensible advice was along the lines of toss that default 14 opposing value out the window and adjust the suggested oppositions accordingly.
A final note for the historical record: The vast majority of decisions in Amberway are made on the basis of Karma, with occasional adversions to Fortune. Now the thing about Everway is that unless you restrict your card readings to pure "good card/bad card," that even Fortune has to be interpreted in the light of Karma or Drama. It strikes me that such dramatinged decisions that get made in the game are influenced far more by symbolism, metaphor and theme than plot as such. I think you could make a fair case that narrativism as you describe it comprehends theme, though symbolism and metaphor seem to bulk small in your model.
Best,
Jim
Logged
Unqualified Offerings
 Looking Sideways at Your World
20' x 20' Room
 Because Roleplaying Games Are Interesting
Epoch
Member
Posts: 201
Algorithms, complexity and what any of this has to do with R
«
Reply #27 on:
June 15, 2001, 01:56:00 PM »
Ron:
A little known, quicklyfailed game by the name of Metascape did the "GM never rolls" deal (players rolled their offense versus a static target number to attack NPC's, and rolled their defense versus a static target number when NPC's attacked them), and, I think, did it one better.
Metascape was unabashed space opera of the most ludicrous degree  it had openended die rolls, and, by openended, I don't mean "if you roll the top number on the die, reroll and add," I mean, "If you roll the top number (16) on the
multiplier
die then reroll the multiplier and toss that into the multiplication as well." So, in the couple of games of Metscape I played, it generally happened a couple of times a session that someone who generally expected to get between, say, a 10 and a 40 on his die roll would get a number in excess of 1,000. I recall having great fun thinking of all the insane things we could do with these ultracritical results.
The "players only roll" rule very neatly dovetailed into this by ensuring that the bad guys could never roll really lucky and blow away a PC, thus reinforcing the game convention of a space opera with heroes.
While Metascape was clunky and silly in many ways, I really think that it had some of the most innovative design of the period in which it was produced (which was roughly '92).
[Edits to remove little typoes]
[ This Message was edited by: Epoch on 20010615 17:58 ]
[ This Message was edited by: Epoch on 20010615 17:58 ]
Logged
Supplanter
Member
Posts: 258
Algorithms, complexity and what any of this has to do with R
«
Reply #28 on:
June 15, 2001, 06:44:00 PM »
Quote
I built the probability distribution for the median rolling mechanism. The value frequencies (the probability of obtaining a roll equal to X) aren't a bell, but rather an inverted parabola (Ax2 + Bx + C = D ), kinda looks like a bell but not quite, it's steeper at the extremes.
The probability for beating a difficulty of X is almost linear, in fact it doesn't change much (less than 10% discrepancy all the way) than that of rolling 1d20 (D&D style) and checking that it's higher than the diff.
If anyobody is actually interested in this I'd be glad to send them the excel sheet I worked on, just email me.
I for one would be greatful to see your Excel sheet, yes  I did mine by brute force, which means, for my d10 calculations, there are a thousand lines of permutations.
Interesting to hear that the result is a true parabola rather than a bell. Now, while it may be steeper at the ends, it's also truncated, so in a sense the end points are fatter than the alternatives. To be clear on what I consider the alternatives, let me say that this started with my desire to turn Fading Suns from failurebasis to successbasis rolls. FS uses a d20. I've learned from some mailing list archives that some FSers, the ones addicted to bell curves, use 2d10s instead of a d20. (Oh and btw, FS, with its separate die pool roll for damage strikes me as a game whose search and handling times are way out of whack for what it seems to want to be. Of course what it wants to be is a combination of Wolfe, Simmons and Silverberg with the serial numbers only partly filed away, but there are worse things.)
The switch from d20 to 2d10 has some serious significance, since 19 is an automatic miss and 20 is a fumble  with a single d20 a fumble has a 5% chance of happening, while with 2d10 there is only a 1% fumble chance. (There's a critical chance in there too, but I forget whether it's on a roll of 1 or on a roll of your exact target number, so leave it aside.)
In FS you otherwise get as many successes as your roll if you roll under your target number, but 0 if you roll over.
That
at least is a handling time dream to do. IOW, if your target number is 14 and you roll 13, you get 13 successes. If you roll 15 you get bupkus. (What happens with successes is a little outside the scope of the subject at hand, so leave it aside.)
My first idea was to use a single d10 instead of a d20 but keep the scores the same and give automatic successes for any points of target number over 10. IOW, if you have a target number of 14, take 4 automatic successes and then add the value of the d10. A roll of 10 would be an automatic failure, the same 10% chance of failure that OTS FS gives you, where 19 or 20 hose you. Then consider a roll to have fumbled only if the character was accenting (trading roll difficulties off for increased chances of minimal success or increased degrees of success depending on the direction you choose to accent).
Since it was clear from reading that some people just love bell curves, and since I consider almost all the existing ways of getting them to be too slow, I thought up the median die idea. It isn't, as you say, a true bell curve. But I don't see it as mostly linear  looking at the d10 curve, once you get outside of 4 or 5 range, the raw chance of success changes by more than 10% in terms of basis points over a linear roll  almost 50 basis points for a target of 2 and more than 70 basis points for a target of 1.
So with the understanding that I consider, say, the median d10 as a replacement for either a single d20 or 2d10, one thing I like is that the end points of the median d10 fall nicely between the end points of the other two options. On a d20, the end point (20) has a 5% chance of occurring. On 210, the end point (also 20) has a 1% chance of occurring. On, um, med(d10), the end point (10) has a 2.8% chance of occuring. So if one thinks 5% is too high a fumble chance and 1% too low, well, 3% is between them.
Quote
Also, if you have any questions regarding prob. distributions of some game system or whatnot, just let me know.
Yes! Since I always envisioned a med(d10) roll as part of an opposedroll pair, how close to a bell curve do you get when high is subtracted from low? Or, to complicate it past the point I would have any right to expect you to spend time on, what about this:
Suppose that each player has a target number that is in the range common to Sorcerer dice pools  say 2 to 7. Say that your median die scores like Fading Suns dice. IOW, my Soma score is 4. I roll median d6 (NOT d10!). If I roll 1, 2, 3, or 4, my result is my roll. If I roll 5 or 6, my result is zero! If my score is 6, my result is my roll unless I roll a 6. If my score is 7, my result is one point (because my score is one more than 6, plus the result of my roll (because my success number is 6), unless I roll a 6  in which case I get 0.
Now someone else is doing the same thing, and we're subtracting higher score from lower to get the number number of victories. If we each get zero successes and tie, the side with the LOWER target number scores one victory. If we both get positive successes and tie (e.g. both roll 2), the side with the HIGHER target number scores one victory.
Now here's the question. How does the
victory spread
compare to the victory spread for Sorc's dice pool method?
Best,
Jim
Logged
Unqualified Offerings
 Looking Sideways at Your World
20' x 20' Room
 Because Roleplaying Games Are Interesting
Don Lag
Member
Posts: 72
Algorithms, complexity and what any of this has to do with R
«
Reply #29 on:
June 15, 2001, 08:37:00 PM »
For the guy with the big SQl tables :smile:
There's a math technique that's pretty useful called Probabilities (I'm not being sarcastic, it's just obvious you aren't too familiarized with it).
The small analysis I made for the median rolls, had nothing to do with writing brute force combination tables. Rather, by using probabilities I arrived that the formula for obtaining a certain value X on a median roll of 3 Nsided dice is:
P(x) = [ 6(x1)(Nx) + 3(N1) + 1 ] / N
^{3}
I made a very small table based on this formula for adding up cases and could get most of the interesting data from it.
I'd be most happy to work on any weird dice mechanics any of you guys come up with (it SEEMS I have a sturdier mathematics background than the rest). I'll be giving a look at the current propositions.
I'll be posting results at
http://www.seba.cl/seba/dMechs
soon.
[ This Message was edited by: Don Lag on 20010616 02:01 ]
Logged
Pages:
1
[
2
]
3
« previous
next »
Jump to:
Please select a destination:

Welcome to the Archives

=> Welcome to the Archives

General Forge Forums

=> First Thoughts
=> Playtesting
=> Endeavor
=> Actual Play
=> Publishing
=> Connections
=> Conventions
=> Site Discussion

Archive

=> RPG Theory
=> GNS Model Discussion
=> Indie Game Design

Independent Game Forums

=> Adept Press
=> Arkenstone Publishing
=> Beyond the Wire Productions
=> Black and Green Games
=> Bully Pulpit Games
=> Dark Omen Games
=> Dog Eared Designs
=> Eric J. Boyd Designs
=> Errant Knight Games
=> Galileo Games
=> glyphpress
=> Green Fairy Games
=> Half Meme Press
=> Incarnadine Press
=> lumpley games
=> Muse of Fire Games
=> ndp design
=> Night Sky Games
=> one.seven design
=> Robert Bohl Games
=> Stone Baby Games
=> These Are Our Games
=> Twisted Confessions
=> Universalis
=> Wild Hunt Studios

Inactive Forums

=> My Life With Master Playtest
=> Adamant Entertainment
=> Bob Goat Press
=> Burning Wheel
=> Cartoon Action Hour
=> Chimera Creative
=> CRN Games
=> Destroy All Games
=> Evilhat Productions
=> HeroQuest
=> Key 20 Publishing
=> MementoMori Theatricks
=> Mystic Ages Online
=> Orbit
=> Scattershot
=> Seraphim Guard
=> Wicked Press
=> Review Discussion
=> XIG Games
=> SimplePhrase Press
=> The Riddle of Steel
=> Random Order Creations
=> Forge Birthday Forum