Reviews and Ramblings
MIDDENARDE - PART 7 by PurpleXVI - 12/12/16
MIDDENARDE - PART 6 by PurpleXVI - 12/12/16
MIDDENARDE - PART 5 by PurpleXVI - 12/12/16
MIDDENARDE - PART 4 by PurpleXVI - 12/12/16
View All Articles
GM Startup Guide by PurpleXVI - 06/10/09
View All Articles
DORF FORT ELLPEE by CAPSLOCKGUY - 10/19/08
View All Articles
So, you want to make a game?
09:21pm EDT - 10/18/2008
Got a concept? Awesome. Written some fluff? Perfect! Decided that you want a stat called Asskicking and a skill for Anal Circumference? That's wonderful.
Now throw all that shit out. It's just going to get in your way. When you want to make a game, you should forget EVERYTHING else until you have finished the very most basic part: Resolution.
How do you resolve shit in your game? For example, in 3rd edition D&D, you roll a D20 to try and get above a certain DC. In the Storyteller system you roll a pile of D10's, and each one above a certain Target Number(henceforth "TN") adds to the level of success.
It sounds basic, and intuitive, to start with this, but it really is not. A lot of people fuck themselves over by saving the actual mechanics of how shit works, on the most basic level, until they've already bogged themselves down with some completely unplanned vision of the REST of the system.
At this point you might say: "Sure, okay. What does it really matter? I'll just use 3d6 or something. GURPS was neat." Firstly, GURPS sucked. Secondly, it matters surprisingly much.
Let's take, for instance, D20 vs the Unisystem. As mentioned before, D20(same system as 3rd edition D&D), rolls a D20(surprise!) you add your modifiers, and if it's above some pre-decided number, you succeed! In the Unisystem, the TN is always 9, you add the relevant stat and skill to a D10, and the more you get above that 9, the more you succeed(mostly critical in combat).
In the Unisystem, the random factor is small compared to the skills and stats(1-5 on both, generally), meaning that your stats matter considerably more than random chance even early on(unless you're totally untrained), and that it takes a relatively low amount of skill to generally succeed unless it's an opposed action. The upshot of this is that planning is more important than chance, because you can generally rely on what you try to go as you plan it, then it's just a matter of understanding the consequences of your actions.
Conversely, in D20, taking it completely without any sort of DM arbitration, the random aspect outweighs your stats for a LONG time unless you're absurdly crunked out at something, effectively meaning that ANY undertaking is rather risky and that planning becomes less vital(because half the time you'll fuck up whatever you're trying to do, anyway.). The lack of a static TN(the DC being rather fluid and up to the DM) also risks causing "stat inflation." That is to say, your odds of failure remain constant no matter how good you are, because there's no upper limit for how difficult anything can be, you do the same things, same risk of failure(unless you decide to skip the story and go pick on peasants), just slightly flashier.
Using multiple dice for your resolution mechanism also means that maximal or minimal results are less likely than average results. This results in something akin to rolling small dice, in that your stats matter more because there's less wild variation in the results you get whan actually rolling.
Now, once you've decided on what dice to use, you need to decide on a couple more things. #1: Do your stats and skills apply a static boost or do they make you roll more dice? #2: Do you want people to succeed often?
"Dice pools" are used by stuff like Storyteller and, again, helps make the crazy results less likely(but they do add more rolling and a bit more work to it). As for success levels... It depends on what people roll for. Is it assumed that they basically snap their fingers and simple stuff just works and you only roll when they're trying to stab that dragon in the eye? Or do you roll for EVERYTHING and the difficult stuff is only when someone's trying to oppose them(the damn dragon doesn't want to get stabbed!)?
And you're still not done. Just rolling to see whether you, say, can pick a lock, is generally simple. But what happens when you get into a fight? This is usually where a lot of games break down completely. Opposed actions. Almost every fight has several opposed actions per round. This is where you want stuff to be as simple as possible. For example, replacing an opponent's Dodge roll with a static penalty to hitting the guy? Less rolls. Static damage reduction from armour rather than rolls to see how much it reduces? Less rolls! You can even go so far as to have static damage, but that reduces one of the more exciting(or nailbiting) elements from combat.
Anyway, this has turned long and incoherent. Here's the TL;DR version. Figure out how the system works and how you want it to work before you get started on anything else. And shit, don't be afraid to adjust an existing system to do what you want it to. There's no reason to reinvent the wheel.