part 2: game system
there is a very distinct focus on 'power' vs. 'technique' in ALL handheld weapon design and usage. I'm simply finding it impossible to capture this without using a system that gives each weapon two additional values: 'power' and 'technique'. The examples are inumerable, but consider the following two classic ones: 2h-sword v estoc and chinese saber v chinese sword are only two, but these are both weapons which are deliberately compared by both users and weapon historians as 'power' v. 'technique'. However, it is wrong to assume technique = skill just as it is wrong to assume power = strength; power can also be related to skill and technique can be related to intrinsic ability to handle weaponry. The word 'dexterity' is actually defined as a measure of expertise or technique. strength and dexterity, power and technique; these are not things you simply have, nor are they things that are simply trained. we know that there are some people who genetically can get stronger faster, just as there are some people who get more 'technique' faster. we can see then that there is really a strong connection between these 'attributes' and the _way_ we learn things. the game system that most notably has utilized this is EVE, which makes a direct relationship between the rate at which you learn skills, and the rating of the relevant attribute. I like this, but I don't like that the attribute has no other effect; it works OK for EVE in which it can literally take years to master a set of skills, but not for an RPG in which players should see a little more affect.
Therefore, my system will have the 'power' and 'technique' weapon parameters. The relationship between the player's attributes and this will be a logit curve of the attribute minus the parameter, multiplied by the parameter; the power parameter of a weapon will be related to strength, and the technique to dexterity. however, a player's skill level is also a logit curve. base skill is x=-5, which is like y=0.01. the effects of str and dex are multiplied by this. therefore, a very strong or dextrious character with no skill facing a weaker, clumsier character with even a little skill may be outmatched. Lastly, each weapon has an 'arms' value. Heavy military weaponry such as the 40 pound polearms may have huge strength requirments, but also have a high arms value. Their is typically a correlation between 'power' and 'arms' value, but not always. However it is hard to escape the fact that military weapons for fighting against heavy armor and horses are very heavy themselves, while civilian and concealable weaponry are typically designed with technique in mind. The logit's constants can be modified to get a desirable curve. they are likely to be flattned a little for str and dex, and even more for the effect of skill on them. it will look a little like this:
Code:
y=((logit(str-pwr) * pwr) + (logit(dex-teq) * teq)) * logit(skill)
actual combat can have more such skill checks included, the details can be worked out and even added on if for some reason it becomes necessary; although I'd like to keep it simple. there may be some indirect skill effects too, like skill for wearing armor or something.
the beautiful thing about this is that ALL skills will use this same system. All skills have some relevant attributes, and the skill level, and they will all use this type of formula to determine applied effect. this means combat is seperated from some kind of level or experience, and is rather just a skill. further, spells will just be skills too. so a spell might involve cognition, or psyche, or spirit, or whatever. but what's more, maybe that spell involves strength too! or dexterity or constitution, and these can be a part of the skill check. the downside is that all these extra parameters have to be assigned, but I think the affect is clear enough and the system simple enough that it should all be very straightforward; and in the end satisfying and elegant.
part 3 is on the way