Hello chaps.

I seem to have hit a devil of a quandary in the development of my game (Echelon, currently sitting in a rather rough alpha state at http://www.latech.co.uk/rpg ) concerning character advancement.

I have settled on the 'currency' of advancement - time - probably to be measured in weeks, although in the current draft it's measured in hours.

However, I have yet to establish how to structure the advancement. I would love to go classless, but I am worried that doing this will yield unacceptable levels of munchkinism.

I have also thought about splitting the advancement structures for physical skills, knowledge and trades in three separate whatevers as well, to encourage at least learning on the part of characters.

Help?

Nothing like setting up an economy.

Munchkinism is going to happen one way or another after a certain point.  You can certainly make it less desirable.  Sectioning off components helps a bit, especially if you make mutually opposing components affect the cost of the other or be in the same section as each other.  This way they'll have the share the same points between the two rather than being able to dedicate separate point pools to each.

If you are using a point system, you'll have to set the price to encourage the behavior you want.  Static costs are good for things that you don't mind players buying multiples of.  Increasing costs are good to place on items which are nice to have, but you don't want the players to solely dump everything into repeatedly without considering the merits of other aspects.

You'll want to do an "Importance Weight Tally" of the upgradable aspects of a character.  List these aspects and find out how much they affect a character's ability to operate and the importance of such.  You'll quickly locate the bits you want to guard from misuse and it'll help in determining how you want to "price" them.  The most valuable are best to put an increasing cost upon.  This cost can be based on the current value of the aspect or just how many times it has been upgraded.  Pick one reason and stick with it to avoid confusion.  Cost based on current score is great for allowing players to caught up less than impressive aspects, but cost based on number of upgrades is good to encourage players to be careful in what they upgrade and how they construct characters.  Increasing linearly is great for nice to have items, and exponential is perfect for REALLY NICE to have items you don't want players to over capitalize on.

Pardon if the advice is pretty general, but the rest is tweaking and experimentation to form the feel of the game you want to cultivate.

Hi Richard,

The answer might be in the why of why you are having character advancement at all? What are you trying to get at with it?

Or; if your just doing character advancement because everyone else does, then it the situation becomes harder - it's like trying to repair a mechanism you didn't even want in the first place.

Make them choose a "Career Path" or two, which is far from the same as a "class", which gives them access to career specific skills, that they need to train at a facility that is built specifically for their career. We will call those schools for the time being, and studying for a skill takes 1 week for the first level, 2 weeks for the next, etcetera.

How you go about career choosing would be another matter which I will leave to rest until you tell me you are interested in the who's and what's.

Besides that, you can have non-career specific skills such as special attacks or spells, that can also be taught at a school, but these are for each and every character. I personally hate exp. points, I think they are stupid, and I would personally make them pay cash to advance, since they are training their skills in a school, which would need the cash to stay open for business. That's what I would do. Hope it helps.

BubbaBrown wrote:
Nothing like setting up an economy.

Munchkinism is going to happen one way or another after a certain point.  You can certainly make it less desirable.  Sectioning off components helps a bit, especially if you make mutually opposing components affect the cost of the other or be in the same section as each other.  This way they'll have the share the same points between the two rather than being able to dedicate separate point pools to each.

If you are using a point system, you'll have to set the price to encourage the behavior you want.  Static costs are good for things that you don't mind players buying multiples of.  Increasing costs are good to place on items which are nice to have, but you don't want the players to solely dump everything into repeatedly without considering the merits of other aspects.

You'll want to do an "Importance Weight Tally" of the upgradable aspects of a character.  List these aspects and find out how much they affect a character's ability to operate and the importance of such.  You'll quickly locate the bits you want to guard from misuse and it'll help in determining how you want to "price" them.  The most valuable are best to put an increasing cost upon.  This cost can be based on the current value of the aspect or just how many times it has been upgraded.  Pick one reason and stick with it to avoid confusion.  Cost based on current score is great for allowing players to caught up less than impressive aspects, but cost based on number of upgrades is good to encourage players to be careful in what they upgrade and how they construct characters.  Increasing linearly is great for nice to have items, and exponential is perfect for REALLY NICE to have items you don't want players to over capitalize on.

Pardon if the advice is pretty general, but the rest is tweaking and experimentation to form the feel of the game you want to cultivate.

Callan wrote:
Hi Richard,

The answer might be in the why of why you are having character advancement at all? What are you trying to get at with it?

Or; if your just doing character advancement because everyone else does, then it the situation becomes harder - it's like trying to repair a mechanism you didn't even want in the first place.

Daniel36 wrote:
Make them choose a "Career Path" or two, which is far from the same as a "class", which gives them access to career specific skills, that they need to train at a facility that is built specifically for their career. We will call those schools for the time being, and studying for a skill takes 1 week for the first level, 2 weeks for the next, etcetera.

How you go about career choosing would be another matter which I will leave to rest until you tell me you are interested in the who's and what's.

Besides that, you can have non-career specific skills such as special attacks or spells, that can also be taught at a school, but these are for each and every character. I personally hate exp. points, I think they are stupid, and I would personally make them pay cash to advance, since they are training their skills in a school, which would need the cash to stay open for business. That's what I would do. Hope it helps.

What I did with Orchestra to solve this problem with a classless system (and it may not be solved, and somewhat relies on the dice/modifier mechanic) is that advancements directly neglect a more juicy spread, meaning nobody has a Combat Monster +5 (unless they really want one, in which case they will be an asset to the team but not a team leader, and still far from immortal). Similarly, with the exception of maybe Weight Lifting there's no skill that can get massive modifiers (and Weight Lifting is used for its namesake, so it won't be too terribly munchkin, it'll just be like an action movie- the character can flip cars, rip massive guns from turrets [should there be guns in turrets, and then it'll require someone with some Science skill to unlock it for him]) and this makes the game more fun, allows a little bit of exceptional characters but still remembers that "no man can outsmart the bullet".

I'd also recommend to look at the health system- it bothers me when health has to be bought separately (the King of Marthin has 5 health because he didn't wanna invest in it?) but I'd definitely link its growth to well-rounded (i.e. not munchkin) selections and activity. Typically when one finds a munchkin, they find that they obsess in one area they feel they do well in (or maybe that's just my brother), for instance playing a character in the CUDA Lord of the Rings game with no fewer than five weapons and full combat skills from the get go, or a Troll Street Samurai in Shadowrun (who, interestingly, neglected Body, but that's user error).

When dealing with something finite like time as an advancement mechanism, I'd be sure to keep in mind that some characters should "waste" time in character. While this definitely makes for a perks/flaws system, you could also do some interesting stuff with short-term bonuses at the cost of long term progression, though that's your call.

Also, the "Importance Weight Tally" is sorta what inspired me to write Orchestra, if it means what I think it does. Basically, if I understood it right, you look at everything and look at how it affects the gameplay. Either make the base number for those common areas (like combat) higher, or make it cost more, or attempt to direct focus away from it. In Orchestra I attempt to do this by making combat extremely lethal (a lot of guns kill starter characters or their buddies in one hit). You could just make all the combatants encountered have something like a +3 bonus to combat during NPC creation (if you have a system) which would mean giving them a slight boost, but then non-combat specialized characters really can't do anything in combat (which is realistic but can be boring or a turn off), or just make it cost double (or do like d20 does and make it be a progression over time, sorta like what I like to do with health).

Richard wrote:
Like I mentioned, I'm not going to be using a points system, but rather the time that has passed in-character (with some GM fudge of course - "You have spent so long reading and learning this ancient language over the past week that you gain a +1 bonus" etc.)

Could you give an example of this Importance Weight Tally thingy that you refer to? I think I understand what you're referring to, but I've never seen such a logic device used in practice before.

Kyles wrote:
What I did with Orchestra to solve this problem with a classless system (and it may not be solved, and somewhat relies on the dice/modifier mechanic) is that advancements directly neglect a more juicy spread, meaning nobody has a Combat Monster +5 (unless they really want one, in which case they will be an asset to the team but not a team leader, and still far from immortal). Similarly, with the exception of maybe Weight Lifting there's no skill that can get massive modifiers (and Weight Lifting is used for its namesake, so it won't be too terribly munchkin, it'll just be like an action movie- the character can flip cars, rip massive guns from turrets [should there be guns in turrets, and then it'll require someone with some Science skill to unlock it for him]) and this makes the game more fun, allows a little bit of exceptional characters but still remembers that "no man can outsmart the bullet".

I'd also recommend to look at the health system- it bothers me when health has to be bought separately (the King of Marthin has 5 health because he didn't wanna invest in it?) but I'd definitely link its growth to well-rounded (i.e. not munchkin) selections and activity. Typically when one finds a munchkin, they find that they obsess in one area they feel they do well in (or maybe that's just my brother), for instance playing a character in the CUDA Lord of the Rings game with no fewer than five weapons and full combat skills from the get go, or a Troll Street Samurai in Shadowrun (who, interestingly, neglected Body, but that's user error).

When dealing with something finite like time as an advancement mechanism, I'd be sure to keep in mind that some characters should "waste" time in character. While this definitely makes for a perks/flaws system, you could also do some interesting stuff with short-term bonuses at the cost of long term progression, though that's your call.

Also, the "Importance Weight Tally" is sorta what inspired me to write Orchestra, if it means what I think it does. Basically, if I understood it right, you look at everything and look at how it affects the gameplay. Either make the base number for those common areas (like combat) higher, or make it cost more, or attempt to direct focus away from it. In Orchestra I attempt to do this by making combat extremely lethal (a lot of guns kill starter characters or their buddies in one hit). You could just make all the combatants encountered have something like a +3 bonus to combat during NPC creation (if you have a system) which would mean giving them a slight boost, but then non-combat specialized characters really can't do anything in combat (which is realistic but can be boring or a turn off), or just make it cost double (or do like d20 does and make it be a progression over time, sorta like what I like to do with health).

BubbaBrown wrote:

Richard wrote:
Like I mentioned, I'm not going to be using a points system, but rather the time that has passed in-character (with some GM fudge of course - "You have spent so long reading and learning this ancient language over the past week that you gain a +1 bonus" etc.)

It's just a different abstraction of points in the end.  Consider points in reference to whatever you have chosen for your units of character development currency.

Could you give an example of this Importance Weight Tally thingy that you refer to? I think I understand what you're referring to, but I've never seen such a logic device used in practice before.

I wanted to debug a problem I had with character attributes.  I wanted to be sure they all had roughly equal importance to avoid have the "wonder" stat and the "dump" stat situation.  So, I listed them and systematically went through and counted each time they were used in the system.  Helped quickly to find attributes that were deviated from the rest.  The same methodology can be used to find out what components of the system are used the most.