Behind on blogging again, but life's twists and turns keep me on my toes lately. I've some extra time tonight, and in order to get to sleep, I think I will muse on Wildly Inadvisable, since I'm back to running it and the skills system has been bothering me quite a bit.
What's the point of a skills system? Well, that is a difficult thing to answer. In broad terms, it is a measure of things your character can do. This can include things such as creating objects, remembering a piece of information, climbing a wall, or casting a spell. In simple terms, this is a pretty easy thing. But taken into gaming terms, it can get pretty complicated, especially since there tend to be two types of skills: Combat skills, and non-combat skills.
In 2nd Edition AD&D, there was a pretty clear divide here. You had a list of Non-Combat abilities, such as Seamanship which got you a host of things like bonuses to swim, and the knowledge of how to work on a boat, but not necessarily run one. It was like how Professions became in d20 Modern - a measure of things your character has done in the past to give them an edge of sorts.
But many systems attempt to lump skills into the same category, and force them to play by the same rules, which can make things quite messy. Therefore, I have come to the realization that my previous dependency on d20-like mechanics is actually hurting the way I have conceived of the skill system for WI. Let's examine this.
How Things Turned Out
The concept behind skills seemed pretty straightforward. You had your attributes, which each had key skills tied to them. From there, these skills had specialties, ranging from resisting a specific type of damage to being able to create a computer virus. In theory, it works great. In practice, it's pretty messy overall, and it is hard to actually find anything in there.
Not to mention the messy amounts of math involved. For every two ranks you place into the basic skill, you can apply a single point to a "specialty", which basically means you gain a higher benefit to a specific instance. For damage resistances or elemental affinities, this is kind of cool. But it makes for a very messy skill sheet, particularly for a game that is supposed to be simplistic.
Fixing The Problem
In order to address this, a few ideas have occurred to me. Instead of an overly-complex system like I have already had set up, one can easily just separate things into combat and non-combat skills. Combat skills are those which do not have a hard 'cap' on them, and are intended to be scaled up as high as possible. Non-combat skills, on the other hand, should have a 'soft cap'. Is it really necessary to have to roll over a 30 to hack a computer database for information that is likely vital to the plot? Not really. So instead, let's have the two follow very different rules, instead of attempting to shoehorn everything into a single category where all the skills play by the same rules.
For lack of a better term, the Non-Combat skills should follow a "pip" system. Let's just say that each of these skills has ten "pips", or ranks that you can put in. Spend a point, get a "pip", similar to how it runs now. However, for every "pip", or maybe every two "pips", you gain an ability tied to that skill. For example, leveling Athletics could grant you a bonus to climbing, or maybe even let you avoid most climbing-based rolls. Or, it could grant you a higher base speed, to reflect your training. Likewise, the computer-based skill can be overhauled as well, so instead of having to roll for the skill, you instead can either perform the requested action if it is well within your ability to do so. Alternatively, treat all non-combat skills as if they had a result of 10. This is important for a second reason, and that is clearing up the combat system, while laying the foundation for the next major thing: Status Effects.
One main issue I have with the system as it is now would be that attempting to add in status effects threatens to slow down game play immensely. Roll Spell Control. Roll Status Defense. Determine whether it beats the target's Defense. Apply Damage and resolve Status Effects. On start of target's turn, roll Status Defense to see if still affected.
This really puts a strain on the combat system, and reminds me of the clunkiness that plagued the d20 system. Instead, I want to apply the above-mentioned "perfect 10" defense, with a bonus caveat: You can have benefits to your status defenses. You can have increased resistances to certain types of Statuses, lessened Status duration, or maybe even mitigate the drawback a Status has on you - perhaps even to the point of an immunity to that particular status. This is a great boon for making good 'villain' or 'monster' templates, which will be very important if the game system is to actually go anywhere. Players will likely not wish to pursue these options, but a monster with nothing to lose might enjoy an immunity to being blinded, poisoned, or even set on fire!
So what determines a "Combat" skill and a "Non-Combat" skill? A "Combat" skill is one that is important in combat, and has no real cap to it. This includes skills such as Resist Status, Dodge, so on and so forth, and may require rolls for it. Non-Combat skills, on the other hand, never have to be rolled, and have a soft-cap, after which point putting more ranks into the skill are pretty much pointless.
I suppose that's enough musing for now, and I covered all the important points I wanted to remind myself of, so that's good for now.
As for modeling stuff: Not sure how much time will be available for this in the near future, but we will see. I may have a contracting job coming available, so time will tell how this works out and whether a change in career is just a pipe dream or a distinct possibility.
No comments:
Post a Comment