Okay, I broke down and wrote a program to generate these, so they are easier to generate. Here are some fairly complete tables for cumulative probabilities using d10 dice pools.
[table=1 Successes]
[tr][th]Net Target[/th][th]2[/th][th]3[/th][th]4[/th][th]5[/th][th]6[/th][th]7[/th][th]8[/th][th]9[/th][th]10[/th][/tr]
[tr][th]DicePool(2,d10)[/th][td]99%[/td][td]96%[/td][td]91%[/td][td]84%[/td][td]75%[/td][td]64%[/td][td]51%[/td][td]36%[/td][td]19%[/td][/tr]
[tr][th]DicePool(3,d10)[/th][td]99.9%[/td][td]99.2%[/td][td]97%[/td][td]94%[/td][td]88%[/td][td]78%[/td][td]66%[/td][td]49%[/td][td]27%[/td][/tr]
[tr][th]DicePool(4,d10)[/th][td]100%[/td][td]99.8%[/td][td]99.2%[/td][td]97%[/td][td]94%[/td][td]87%[/td][td]76%[/td][td]59%[/td][td]34%[/td][/tr]
[tr][th]DicePool(5,d10)[/th][td]100%[/td][td]100%[/td][td]99.8%[/td][td]99%[/td][td]97%[/td][td]92%[/td][td]83%[/td][td]67%[/td][td]41%[/td][/tr]
[tr][th]DicePool(6,d10)[/th][td]100%[/td][td]100%[/td][td]99.9%[/td][td]99.6%[/td][td]98%[/td][td]95%[/td][td]88%[/td][td]74%[/td][td]47%[/td][/tr]
[tr][th]DicePool(7,d10)[/th][td]100%[/td][td]100%[/td][td]100%[/td][td]99.8%[/td][td]99.2%[/td][td]97%[/td][td]92%[/td][td]79%[/td][td]52%[/td][/tr]
[tr][th]DicePool(8,d10)[/th][td]100%[/td][td]100%[/td][td]100%[/td][td]99.9%[/td][td]99.6%[/td][td]98%[/td][td]94%[/td][td]83%[/td][td]57%[/td][/tr]
[/table]
[table=2 Successes]
[tr][th]Net Target[/th][th]2[/th][th]3[/th][th]4[/th][th]5[/th][th]6[/th][th]7[/th][th]8[/th][th]9[/th][th]10[/th][/tr]
[tr][th]DicePool(2,d10)[/th][td]81%[/td][td]64%[/td][td]49%[/td][td]36%[/td][td]25%[/td][td]16%[/td][td]9%[/td][td]4.0%[/td][td]1.0%[/td][/tr]
[tr][th]DicePool(3,d10)[/th][td]97%[/td][td]90%[/td][td]78%[/td][td]65%[/td][td]50%[/td][td]35%[/td][td]22%[/td][td]10%[/td][td]2.8%[/td][/tr]
[tr][th]DicePool(4,d10)[/th][td]99.6%[/td][td]97%[/td][td]92%[/td][td]82%[/td][td]69%[/td][td]52%[/td][td]35%[/td][td]18%[/td][td]5%[/td][/tr]
[tr][th]DicePool(5,d10)[/th][td]100%[/td][td]99.3%[/td][td]97%[/td][td]91%[/td][td]81%[/td][td]66%[/td][td]47%[/td][td]26%[/td][td]8%[/td][/tr]
[tr][th]DicePool(6,d10)[/th][td]100%[/td][td]99.8%[/td][td]99%[/td][td]96%[/td][td]89%[/td][td]77%[/td][td]58%[/td][td]34%[/td][td]11%[/td][/tr]
[tr][th]DicePool(7,d10)[/th][td]100%[/td][td]100%[/td][td]99.6%[/td][td]98%[/td][td]94%[/td][td]84%[/td][td]67%[/td][td]42%[/td][td]15%[/td][/tr]
[tr][th]DicePool(8,d10)[/th][td]100%[/td][td]100%[/td][td]99.9%[/td][td]99.1%[/td][td]96%[/td][td]89%[/td][td]74%[/td][td]50%[/td][td]19%[/td][/tr]
[/table]
[table=3 Successes]
[tr][th]Net Target[/th][th]2[/th][th]3[/th][th]4[/th][th]5[/th][th]6[/th][th]7[/th][th]8[/th][th]9[/th][th]10[/th][/tr]
[tr][th]DicePool(3,d10)[/th][td]73%[/td][td]51%[/td][td]34%[/td][td]22%[/td][td]13%[/td][td]6%[/td][td]2.7%[/td][td]0.8%[/td][td]0.1%[/td][/tr]
[tr][th]DicePool(4,d10)[/th][td]95%[/td][td]82%[/td][td]65%[/td][td]48%[/td][td]31%[/td][td]18%[/td][td]8%[/td][td]2.7%[/td][td]0.4%[/td][/tr]
[tr][th]DicePool(5,d10)[/th][td]99.1%[/td][td]94%[/td][td]84%[/td][td]68%[/td][td]50%[/td][td]32%[/td][td]16%[/td][td]6%[/td][td]0.9%[/td][/tr]
[tr][th]DicePool(6,d10)[/th][td]99.9%[/td][td]98%[/td][td]93%[/td][td]82%[/td][td]66%[/td][td]46%[/td][td]26%[/td][td]10%[/td][td]1.6%[/td][/tr]
[tr][th]DicePool(7,d10)[/th][td]100%[/td][td]99.5%[/td][td]97%[/td][td]90%[/td][td]77%[/td][td]58%[/td][td]35%[/td][td]15%[/td][td]2.6%[/td][/tr]
[tr][th]DicePool(8,d10)[/th][td]100%[/td][td]99.9%[/td][td]99%[/td][td]95%[/td][td]86%[/td][td]68%[/td][td]45%[/td][td]20%[/td][td]3.8%[/td][/tr]
[/table]
[table=4 Successes]
[tr][th]Net Target[/th][th]2[/th][th]3[/th][th]4[/th][th]5[/th][th]6[/th][th]7[/th][th]8[/th][th]9[/th][th]10[/th][/tr]
[tr][th]DicePool(4,d10)[/th][td]66%[/td][td]41%[/td][td]24%[/td][td]13%[/td][td]6%[/td][td]2.6%[/td][td]0.8%[/td][td]0.2%[/td][td]0.0%[/td][/tr]
[tr][th]DicePool(5,d10)[/th][td]92%[/td][td]74%[/td][td]53%[/td][td]34%[/td][td]19%[/td][td]9%[/td][td]3.1%[/td][td]0.7%[/td][td]0.0%[/td][/tr]
[tr][th]DicePool(6,d10)[/th][td]98%[/td][td]90%[/td][td]74%[/td][td]54%[/td][td]34%[/td][td]18%[/td][td]7%[/td][td]1.7%[/td][td]0.1%[/td][/tr]
[tr][th]DicePool(7,d10)[/th][td]99.7%[/td][td]97%[/td][td]87%[/td][td]71%[/td][td]50%[/td][td]29%[/td][td]13%[/td][td]3.3%[/td][td]0.3%[/td][/tr]
[tr][th]DicePool(8,d10)[/th][td]100%[/td][td]99%[/td][td]94%[/td][td]83%[/td][td]64%[/td][td]41%[/td][td]19%[/td][td]6%[/td][td]0.5%[/td][/tr]
[/table]
[table=5 Successes]
[tr][th]Net Target[/th][th]2[/th][th]3[/th][th]4[/th][th]5[/th][th]6[/th][th]7[/th][th]8[/th][th]9[/th][th]10[/th][/tr]
[tr][th]DicePool(5,d10)[/th][td]59%[/td][td]33%[/td][td]17%[/td][td]8%[/td][td]3.1%[/td][td]1.0%[/td][td]0.2%[/td][td]0.0%[/td][td]0.0%[/td][/tr]
[tr][th]DicePool(6,d10)[/th][td]89%[/td][td]66%[/td][td]42%[/td][td]23%[/td][td]11%[/td][td]4.1%[/td][td]1.1%[/td][td]0.2%[/td][td]0.0%[/td][/tr]
[tr][th]DicePool(7,d10)[/th][td]97%[/td][td]85%[/td][td]65%[/td][td]42%[/td][td]23%[/td][td]10%[/td][td]2.9%[/td][td]0.5%[/td][td]0.0%[/td][/tr]
[tr][th]DicePool(8,d10)[/th][td]99.5%[/td][td]94%[/td][td]81%[/td][td]59%[/td][td]36%[/td][td]17%[/td][td]6%[/td][td]1.0%[/td][td]0.0%[/td][/tr]
[/table]
And for damage dice:
[table=Average Damage]
[tr][th]Net Target[/th][th]3[/th][th]4[/th][th]5[/th][th]6[/th][th]7[/th][th]8[/th][th]9[/th][th]10[/th][/tr]
[tr][th]DicePool(3,d10)[/th][td]2.4[/td][td]2.1[/td][td]1.8[/td][td]1.5[/td][td]1.2[/td][td]0.9[/td][td]0.6[/td][td]0.3[/td][/tr]
[tr][th]DicePool(4,d10)[/th][td]3.2[/td][td]2.8[/td][td]2.4[/td][td]2.0[/td][td]1.6[/td][td]1.2[/td][td]0.8[/td][td]0.4[/td][/tr]
[tr][th]DicePool(5,d10)[/th][td]4.0[/td][td]3.5[/td][td]3.0[/td][td]2.5[/td][td]2.0[/td][td]1.5[/td][td]1.0[/td][td]0.5[/td][/tr]
[tr][th]DicePool(6,d10)[/th][td]4.8[/td][td]4.2[/td][td]3.6[/td][td]3.0[/td][td]2.4[/td][td]1.8[/td][td]1.2[/td][td]0.6[/td][/tr]
[tr][th]DicePool(7,d10)[/th][td]5.6[/td][td]4.9[/td][td]4.2[/td][td]3.5[/td][td]2.8[/td][td]2.1[/td][td]1.4[/td][td]0.7[/td][/tr]
[tr][th]DicePool(8,d10)[/th][td]6.4[/td][td]5.6[/td][td]4.8[/td][td]4.0[/td][td]3.2[/td][td]2.4[/td][td]1.6[/td][td]0.8[/td][/tr]
[/table]
Note that average damage is always directly proportional to the size of dice pool and likelihood of damaging with a single die.
Woah... After only a cursory glance, I'm seeing a much smoother transition. I think d10s might actually be worth a shot.
By the way, thanks. You know most of this math is beyond me.
Okay, I'm going to go on the assumption of abilities between seven and ten, target numbers between twelve and sixteen, and 5d10 dicepools, with successes between one and five (though keep in mind that combat is generally between 12 and 15 with between two and four successes to hit). That said, I'll start with ability scores to see how difficult a number of tasks may be.
[spoiler=7]
1DC12=99%->99.6%->99.8%-99.9%
2DC12=91%->96%->98%->99.1%
3DC12=68%->82%->90%->95%
4DC12=34%->54%->71%->83%
5DC12=8%->23%->42%->59%
1DC13=97%->98%->99.2%->99.6%
2DC13=81%->89%->94%->96%
3DC13=50%->66%->77%->86%
4DC13=19%->34%->54%->71%->83%
5DC13=3.1%->11%->23%->36%
1DC14=92%->95%->97%->98%
2DC14=66%->77%->84%->89%
3DC14=32%->46%->58%->68%
4DC14=9%->18%->29%->41%
5DC14=1%->4.1%->10%->17%
1DC15=83%->88%->92%->94%
2DC15=47%->58%->67%->74%
3DC15=16%->26%->35%->45%
4DC15=3.1%->7%->13%->19%
5DC15=0.2%->1.1%->2.9%->6%
1DC16=67%->74%->79%->83%
2DC16=26%->34%->42%->50%
3DC16=6%->10%->15%->20%
4DC16=0.7%->1.7%->3.3%->6%
5DC16=0%->0.2%->0.5%->1%
[/spoiler]
[spoiler=8]
1DC12=99.8%->99.9%->100%->100%
2DC12=97%->99%->99.6%->99.9%
3DC12=84%->93%->97%->99%
4DC12=53%->74%->87%->94%
5DC12=17%->42%->65%->81%
1DC13=99%->99.6%->99.8%->99.9%
2DC13=91%->96%->98%->99.1%
3DC13=68%->82%->90%->95%
4DC13=34%->54%->71%->83%
5DC13=8%->23%->42%->65%->81%
1DC14=97%->98%->99.2%->99.6%
2DC14=81%->89%->94%->96%
3DC14=50%->66%->77%->86%
4DC14=19%->34%->50%->64%
5DC14=3.1%->11%->23%->36%
1DC15=92%->95%->97%->98%
2DC15=66%->77%->84%->89%
3DC15=32%->46%->58%->68%
4DC15=9%->18%->29%->41%
5DC15=1%->4.1%->10%->17%
1DC16=83%->88%->92%->94%
2DC16=47%->58%->67%->74%
3DC16=16%->26%->35%->45%
4DC16=3.1%->7%->13%->19%
5DC16=0.2%->1.1%->2.9%->6%
[/spoiler]
[spoiler=9]
1DC12=100%->100%->100%->100%
2DC12=99.3%->99.8%->100%->100%
3DC12=94%->98%->99.5%->99.9%
4DC12=74%->90%->97%->99%
5DC12=33%->66%->85%->94%
1DC13=99.8%->99.9%->100%->100%
2DC13=97%->99%->99.6%->99.9%
3DC13=84%->93%->97%->99%
4DC13=53%->74%->87%->94%
5DC13=17%->42%->65%->81%
1DC14=99%->99.6%->99.8%->99.9%
2DC14=91%->96%->98%->99.1%
3DC14=68%->82%->90%->95%
4DC14=34%->54%->71%->83%
5DC14=8%->23%->42%->59%
1DC15=97%->98%->99.2%->99.6%
2DC15=81%->89%->94%->96%
3DC15=50%->66%->77%->86%
4DC15=19%->34%->50%->64%
5DC15=3.1%->11%->23%->36%
1DC16=92%->95%->97%->98%
2DC16=66%->77%->84%->89%
3DC16=32%->46%->58%->68%
4DC16=9%->18%->29%->41%
5DC15=1%->4.1%->10%->17%
[/spoiler]
[spoiler=10]
1DC12=100%->100%->100%->100%
2DC12=100%->100%->100%->100%
3DC12=99.1%->99.9%->100%->100%
4DC12=92%->98%->99.7%->100%
5DC12=59%->89%->97%->99.5%
1DC13=100%->100%->100%->100%
2DC13=99.3%->99.8%->100%->100%
3DC13=94%->98%->99.5%->99.9%
4DC13=74%->90%->97%->99%
5DC13=33%->66%->85%->94%
1DC14=99.8%->99.9%->100%->100%
2DC14=97%->99%->99.6%->99.9%
3DC14=84%->93%->97%->99%
4DC14=53%->74%->87%->94%
5DC14=17%->42%->65%->81%
1DC15=99%->99.6%->99.8%->99.9%
2DC15=91%->96%->98%->99.1%
3DC15=68%->82%->90%->95%
4DC15=34%->54%->71%->83%
5DC15=8%->23%->42%->59%
1DC16=97%->98%->99.2%->99.6%
2DC16=81%->89%->94%->96%
3DC16=50%->66%->77%->86%
4DC16=19%->34%->50%->64%
5DC16=3.1%->11%->23%->36%
[/spoiler]
Um, snake? When you get the time, would you mind updating 2s. When it comes to 10, they may become important.
Heh. For Exalted, I'd need tables for dice pools up to 30 dice...
Well, I'm not going to post tables for 30 dice. But I do have a little Java program to generate as many as you please.
I'll update the tables with 2's, I'll just need to find the time.
Quote from: snakefingWell, I'm not going to post tables for 30 dice. But I do have a little Java program to generate as many as you please.
I'll update the tables with 2's, I'll just need to find the time.
Thanks, but please don't bother on my behalf - I don't really need them.
Besides, Exalted further complicated things by equating a rolled "10" with
two successes..
Oh God... is this really starting to look like Exalted?
Okay, I edited the tables to include more data.
I think d10 pools might work okay. We need to run through mock combat or stat analysis for a bunch of scenarios. I'm thinking things like the following (for melee only, right now):
A couple of schlubs, unarmored, slugging each other with fists.
A couple of evenly matched average guards/soldiers.
An average guard against a low-level PC character.
A couple well-matched high-level fighting types.
Well-matched fighting types, but who have taken different approaches to combat (e.g., tank vs. duelist, tank vs. damage machine, etc.).
Low level character against an animal or monster like a wolf or something.
Once we think we've got something that works okay for one-on-one combats, then we could start looking at mock combats with two-on-one, ten-on-one, etc. But start out with the simple stuff to make sure we understand the basics.
Okay, I'm going to put up 10 soon.
Here's a breakdown of how combat should work:
Melee Attack: Pool and Strength vs. Ref+5
Ranged Attack: Pool and Coord vs. Ref+5
Required successes is determined by armor (2 for light, 3 for medium, 4 for heavy). On a roll of five, damage roll is for instakill (see weapon stats).
Melee damage: Pool and strength vs. Tough+5
Ranged damage: Pool and Coord vs. Tough+5
Damage equals number of successes.
Instakills are rolled like damage, except that a certain number of successes (determined by the weapon) kills. Instakills are rolled on five attack successes (see above) or when the attacked has no hit points.
Weapons: Weapons that deal less damage should also cost fewer action points to use. Characters can also buy AP decreases to attack more frequently.
Armor: Armor penalizes action points. Defense slightly impairs offense.
Action out of turn: Characters can reserve up to five action points to act out of turn later. If their next turn comes and they have not spent their points, they do not carry over. On the flipside, a character can act out of turn unprepared, but it costs five action points to do so.
Just some thoughts.
[blockquote=Armor]Required successes is determined by armor (2 for light, 3 for medium, 4 for heavy).
...Damage equals number of successes.[/blockquote]
Seems like it makes more sense to say that armor absorbs the indicated number of successes/damage. Otherwise you have the odd situation where it is very hard to hit someone in good armor, but if you do, it is automatically devastating.
[blockquote=Insta-kill]On a roll of five, damage roll is for instakill (see weapon stats).[/blockquote]
Would this make more sense to treat it like a WP/VP critical - bypassing the vitality points? I'm not fond of insta-kill.
[blockquote=Weapons]Weapons that deal less damage should also cost fewer action points to use. Characters can also buy AP decreases to attack more frequently.[/blockquote]
I'm open to this. But you have to be careful - reducing AP costs for weapons can sometimes have drastic effects. Maybe better to just buy more AP.
Simple, basic AP systems are okay, but it can get out of hand pretty quickly. Ysgarth used an AP system for attack, defense, movement, spells - everything - and it was one of the most heavily criticized aspects in playtest.
In terms of armor, it only goes as high as four successes... nobody's becoming impossible to hit... it's just that one success, even at an exaggerated target number, is pretty freaking likely. I say we try out "number of successes" armor before we move on to straight DR. Though the latter does mesh better with a couple of my variant ideas (see discussion thread).
In terms of AP... I guess we don't *have* to have out of turn action... but I'm just so fond of it. Lots of my favorite tactics in DnD concern readied actions and AoOs. I would stick with reducing costs. You might only get so far with it (two attacks for an uber-damager, maybe three with something lighter)... but it just feels more right. IMHO it's a little easier than how DnD does it, determining how much you can do in a round.
As for instakill vs. VP/WP... I don't know so much. I'm a big fan of it in d20, but for us? If we do, it might have to be more or less often. Even five successes is pretty common at target number 2. But REALLY freaking rare for anyon else.
Also on successes, I have to say you're quoting out of context. You roll to hit separately from your roll to damage. Hell, the pools aren't even necessarily the same size.
Let's say I attack. I roll 5d10. I succeed three times. That's enough, I hit.
I roll damage. This is a nice little 10d10 weapon, so I roll that. This guy's got low toughness, so I get seven successes. Therefore seven damage.
Understand?
Gotcha. I misread your earlier post - I thought you were suggesting changing that. It makes more sense this way.
Okay, score ten is up.
I might also rehash these by difficulty/score.
Okay, so some stuff on character, armor, and weapon stats:
Ability scores start at seven each. Three points to distribute freely.
Light armor requires two successes and has a 1AP penalty.
Medium armor requires three successes and has a 2AP penalty.
Heavy armor requires four successes and has a 3AP penalty.
Low damage weapons (three dice) cost 3 AP to attack.
Mid damage weapons (five dice) cost 5 AP to attack.
High damage weapons (seven dice) cost 7 AP to attack.
Just some thoughts, really. Maybe there could be a buyable ability that would reduce attack costs by one for a weapon group (to a minimum of 2 of course)... Just a thought.
Also, weapon damage and armor DR could scale in proportion to tech level? Maybe?
And for starts 10 hp.
Okay, we'll try this then for our first combat scenario:
Two chumps, unarmored, beating each other with fists. Assume all stats are average. Assuming one success needed for unarmored? Anyway, the exact values of stats won't matter here as long as everyone is the same.
Also I'll assume that basically unskilled they'll get 4d10 attack pools? And damage for untrained unarmed is 2d10?
Anyway, given that, they'll need 5's to hit, and one success, so that gives them a 97% chance to hit.
They'll also need 5's for damage, so with 2d6 damage pool, they'll average 1.2 damage a round. Although maybe 2d10 is too generous for unarmed damage?
I'm wondering if maybe the base target required here should be 7? Or maybe 6? To reduce slightly the base chance to hit. If the base target was 7, then characters with the same stats would have the following chance to hit with 5d10 pools:
unarmored (1 success): 92%
light armor (2 successes): 66%
medium armor (3 successes): 32%
heavy armor (4 successes): 9%
*shrug* It's hard to say what is best. Need to just pick something and stick with it for the rest of the sims.
Just out of curiosity here...but why exactly are we reinventing the wheel? The WoD has a nice generic d10 based system that just so happens to be the second most used gaming system in the world (right behind D20).
From personal experience, I can say it works well enough as it is (not without its flaws mind you, but fewer than D&D IMO), and I would think it would be much easier to use that as the framework for your excercise. WoD rules can in fact be used to run a fantasy game (I have done so), if you prefer a more lethal, gritty, and dangerous type of setting. Heck Exalted already is a medeival wuxia/fantasy game using a similar system (though I HATE the setting).
I applaud your efforts here, but what precisely is the reason for this approach (as opposed to tweaking a system that already does this, to suit the flavor of your game)? Seems to me like you are making more work than is actually necessary, or am I missing something?
-Nasty-
P.S. this is not criticism, it is a sincere inquiry.
Not sure about exalted or WoD, but I've heard Exalted uses too many dice (as in the above request for 30d10 pool from Kalos Mer). We've pretty much done this from the ground up, I without any knowledge of anything outside DnD and GURPS.
As for why use a new system? Why not?
Hell, we could even include new supplemental rules in the CBGuide.
Anyway, even if the CBG doesn't use it, I know I will.
Also, you might put this in the discussion thread... this one's for number crunching. Yay numbers.
So, snakefing... no rush, but how's that combat sim coming along?
Sorry, but you know the only real reason I'm so impatient at this stage is 'cause I can't really do anything till I know what I'm doing. Seriously, I've got ideas just swimming in my head about mech games, horror games, supers games, variant rules, and all kinds of stuff...
Can't do much till the basics are hammered out though.
I hear you.
Unfortunately, our company just signed a large deal to deliver some software for some portable devices, to be delivered at end of year. That's on top of our normal release cycle, and a research project we're doing. Since we only have three developers, it is really really keeping me busy.
On top of that, the one-year-olds are keeping me busy - up at 6 am to get them dressed and off to day care, work for an hour, shower and get dressed, go to work, home at 5, make dinner for the boys, play with them for an hour, bathe them and read a story, finally get some time for myself around 8 pm. Answer emails, 50% chance my project manager is on IM asking me questions, well, you get the picture.
It will get done, just can't say when.
Okay. Just making sure I'm not the only one left...
But, man, kids... I've got sisters so I know what you mean... and it doesn't get any easier.
Okay, let's try some combat between armed and armored opponents.
I'll assume a couple of basic guard types, armed with some kind of gladius or other short sword (3d10 damage pools) and armored with some kind of cuirass or studded leather (light armor, 2 successes required).
For the first pass, I'll assume that neither of them is out of the ordinary in STR, COORD, REACT, TOUGH. So no net bonuses on any attacks. I'll also assume they have basic training (5d10 attack pools).
Based on the last posted formulas, this would require a 5+ for success, 2 successes, on 5d10 pool. A 91% probability. I'm thinking this is too high, so I'm going to assume 7+ for success instead. That's 66%.
I'm still assuming a 5+ for success to do damage. That's a 60% chance per die to do damage. Overall, they'll average 1.2 damage per round. If we assume the equivalent of 10 VP and 3 WP each, this means on average they'll go about 8 rounds before they get to WP, and 2-3 rounds after that to death.
To check the variability, I'm going to run 5 simulated combats between these two, to check the outcomes.
In the first sim, one combatant drops the other in round 9, and is left with 0 VP and full WP.
In the second sim, one combatant drops the other in round 10, and is left with 5 VP and full WP.
In the third sim, one combatant drops the other in round 7, and is left with 5 VP and full WP.
In the fourth sim, one combatant drops the other in round 14, and is left with 0 VP and 2 WP.
In the fifth sim, one combatant drops the other in round 8, and is left with 5 VP and full WP.
Don't know what to say, except this seems like an acceptable amount of variability. If you want a little more deadliness, you could either increase the damage potential, decrease the base target number to 6, or decrease total VP/WP. These changes could also affect the amount of variability, or course.
Duplicate post somehow
Wow... YUSS. It's crazy to see this actually working. This is just awesome.
For number to hit, I think 6 would be good in both cases. It'll speed things up in hitting and slow things down in damage. Also, let's just work with hit points for now. We'll work with things like wound points later.
An alternative dice pool system:
Rolling the attempt
Non-opposed actions
Dice pool: 3 dice + skill dice + bonus/penalty dice
Target number: pretty much fixed around 8. Possibly this could be increased to as much as 10 for very extraordinary actions. For now, just assume it is fixed at 8. The target number does not represent the difficulty of success. Iâ,¬,,¢d only adjust it to represent certain types of classes of actions that are so unusual (like, perhaps, arcane or psionic manipulations?) that successes are harder to achieve.
Difficulty: The difficulty of the task is expressed in terms of number of successes needed. (Alternatively, you can imagine that this represents the number of successes cancelled out by the task difficulty.)
Results: If you meet or exceed the required successes, you are nominally successful in your task. If you do not, you nominally fail. Higher or lower number of successes can be used to further refine the outcome.
Opposed actions (including combat)
These are the same, except that the difficulty is always enhanced by the opponentâ,¬,,¢s results (number of successes) in a similar check.
For combat, the base difficulty is always 1 success required. The attacker rolls to hit, and the defender rolls to defend. The defenderâ,¬,,¢s successes effectively cancel out the attackerâ,¬,,¢s successes.
Damage
Dice pool determined by the weapon, with bonus dice for enchanted weapons, and Strength or similar characteristic. You must succeed in your attack to roll damage. Add a bonus die for every additional success on your attack roll? Target number is still 8, armor provides a defensive adjustment that is effectively DR, canceling out between 0 and 3 damage successes. Each success deals a single point of damage.
Interpretation of results
On this table, compare the actual successes against the number required to determine the net number of successes. This provides a rough measure of the degree of success.
[table=Action Results]
[tr][th]Net Successes[/th][th]Result[/th][/tr]
[tr][td]-3[/td][td]Critical failure[/td][/tr]
[tr][td]-2[/td][td]Complete failure[/td][/tr]
[tr][td]-1[/td][td]Failure[/td][/tr]
[tr][td]0[/td][td]Success[/td][/tr]
[tr][td]+1[/td][td]Complete Success[/td][/tr]
[tr][td]+2[/td][td]Critical Success[/td][/tr]
[/table]
Critical failure: Something went wrong, making things worse than before. Critical failure should not be too harsh â,¬' you donâ,¬,,¢t want to discourage people from trying.
Complete failure: Something went wrong, usually preventing a retry or some other mild consequence.
Failure: You did not achieve your aim, although you might gain some modest insight or partial benefit for the effort.
Success: You achieved your aim, but perhaps not as smoothly or completely as desired.
Complete Success: You achieved your aim completely and easily.
Critical Success: Not only did you achieve your aim, but you may have done so unusually quickly, or gained some minor additional benefit.
Penalty and bonus dice
Bonuses and penalties can be applied to increase or decrease the number of dice in the dice pool. Typically bonus dice may be gained due to traits or characteristics. Bonuses or penalties may accrue due to circumstances that are favorable or detrimental to the character.
Certain feats or options might allow characters to gain bonus dice in certain circumstances, or give them the option to take penalty dice in return for some alternative benefit. E.g., something like Power Attack might let the character take a penalty die on their attack in order to gain two bonus dice on their damage roll.
Why do it this way?
Using opposed rolls for combat allows for a comparative roll that gives advantage to the more skilled, but with less chance of hitting the impossibility limit.
For example, if a character is attacking with five dice, and the defender has ten dice, thereâ,¬,,¢s obviously an advantage to the defender. The attacker will average 1.5 successes and the defender will average 3 successes. This makes the attacker unlikely to hit, but it is still possible. Adding more dice to the defenderâ,¬,,¢s pool makes it harder and harder, but never quite impossible.
If we used the defenderâ,¬,,¢s skill to directly change either the target number or the number of successes required, youâ,¬,,¢d quickly hit the limit where the attacker literally has no chance to succeed. Avoiding this limit would probably require using larger dice pools, making the rolls
Whatâ,¬,,¢s bad about this?
In combat, this means that every attack involves two dice pool rolls that need to be compared. Neither roll is particularly difficult, but it could create a procedural bottleneck in actual play, with players waiting around for the GM to roll defense against their attacks.
The bottleneck could be avoided if you allow players to roll both attack and defense simultaneously. For example, use red dice for attack dice and white for defense, then roll them all at once, using the white successes to cancel red successes. Of course, this requires the GM to tell the players how many dice their foes are using for defense, which some people may not prefer.
Mechanically this seems sound, but it may suffer from playability problems.
I guess it could work.
I personally don't like opposed rolls as much. I'm especially leery of a system that relies on them, but I guess it's a matter of taste.
Any chance of a similar breakdown of the "roll under ability 5d10+skill rank" idea I've been mulling over?
TN
Abilities run from 5 to 9. You have 4 mental stats and 4 physical stats. In each category, you start at 5 and have 4 points to distribute. TN is at or under ability score.
Successes
The number of successes is determined by the difficulty of the task.
When trying to beat someone (sneak past them, hit them in combat, etc.) You have to succeed a number of times according to their modifier. Modifiers are half the relevant ability rounded down.
Dice
Dice start at 5d10. You add one die for each rank you have in the relevant skill. Generally, you don't get more than three ranks in any one skill.
Example
A gunslinger with Coord7 and two ranks in Ranged(Firearms) wants to hit a monk with Reflex7. The gunslinger must roll 7d10 to roll at or under 7 at least 3 times.
He hits 77% of the time (I think... I may be wrong).
Good
Everything varies without being too terribly confusing. The player knows how many dice he rolls and what his TN is. The only information to be relayed to the GM is how many successes.
Bad
There isn't really any way to scale the defensive side of combat. At higher levels combat might move too quickly. A slight diferrence in power in one variable (dice or score) might not make too much of a diferrence, but a slight diferrence in two variables (dice and score) might do ALOT.
I'm a little nervous about playing with opposed rolls too, for the reasons I posted above. I don't have a problem with it in concept, but as a practical matter I'm not sure if it would slow the game too much.
For your gunslinger, I'm getting 97%. Rolling 7 or lower is the same probability as rolling 4 or higher, so by the tables above the odds of getting 3+ successes on 7 dice against target number 4 are 97%. The average number of successes rolling 7 or less on 7 dice are {7 dice * 0.7 success prob) = 4.9.
Of course, these numbers don't take into account the effects of the damage roll.
Quote from: 4.9.
Of course, these numbers don't take into account the effects of the damage roll.
[/quoteReally? Granted, this is pretty awesome as gunslingers go (he's probably taken some heavy hits to other ability scores... likely strenght and toughness... and he's taken two ranks... which is pretty high considering the "max 3" thing) but that is pretty rough.
If we could find a way for defense to scale that'd be good.
Maybe abilities at 3-7? Maybe "modifiers" run...
3=2
4=3
5=3
6=4
7=4
...One half plus one. It's a tad bit more work, but it only needs done once. Then it's just on the character sheet for quick reference.
And then maybe some way to scale defense.
[blockquote=beejazz]Ever played DnD with the defense check variant? I tried it once. Trust me, while opposed rolls are okay sometimes, you don't want to do it as often as once per round.[/blockquote]Lack of damage rolls makes it manageable. This can be achieved through fixed damage or damage somehow tied to the degree of success of the attack roll (e.g. weapon base + degree of success).
Also, as I posted in the other dice pool thread, having three things change in the resolution system is very fiddly and not really valuable. People won't understand it intuitively.