The main Experience Point (X.P.) awards discussions seem to be based around two things: Either you get X.P.for finding treasure or you do not. I tend not to give X.P. for treasure, but I also tend to award experience a little differently that what it tells you in the rules.
The TSR days (and various editions) of Dungeons & Dragons all awarded X.P. for two things: finding treasure (especially magical treasure), and slaying monsters. Now, while not bad in and of itself, this led to some players doing very bad things (like slaying townsfolk or other PCs) to get experience. The sad thing is, there were some Dungeon Masters who let them get away with it. It says normal men are worth a certain amount of X.P. in the Monster Manual, so those who went by the book just awarded the experience, threw up their hands, and wondered what went wrong.
Well, aside from the fact that those Dungeon Masters needed to put their collective feet down, and the "angry mob rule" from Original D&D never made it into the later rulebooks, it seems as if some campaigns degenerated into "kill the monster, take its stuff." As if one single part of the rules had become the whole point of the game.
Certainly many computer RPGs pretty well took that route. There were several articles and letters in Dragon Magazine (in its early days, at least) that dealt with the hack and slash aspect, and whether it had a place in D&D.
But interestingly enough, around the time of Dungeons & Dragons 2nd Edition (2e), 1989, there was a computer game called Baldur's Gate, loosely based on the 2e ruleset. In this game you had various tasks to perform, and the rewards included XP. I had never seen that before, but it made sense to me. Torment did the same, as well as Icewind Dale, which is why those games appealed to me despite my dislike of AD&D. At that time, I was playing Call of Cthulhu, Cyberpunk, Warhammer, RoleMaster, etc.
Time passed, and 3E was released. Even its experience system, with its Challenge Ratings, was skewed in much the same direction as its TSR predecessors. According to designer George Strayton, WotC stuck to the "kill 'em all, take their stuff" philosophy when designing 3rd Edition D&D. They did add one thing, you received experience for disarming traps, but still their X.P. system felt woefully incomplete.
Looking at Rolemaster and Palladium, the way you gain X.P. is far different than in other similar games. in RoleMaster you can gain experience for adventures, and some of the equations to calculate experience are overblown. Likewise, Palladium gives out experience for planning, and you get more if your plan worked, and less if it failed, etc. Both of these are germs of a good idea. What if, like Baldur's Gate (and the much more recent Gothic series), you got experience for doing things? Bring a nobleman back his amulet from the brothel he left it at: 50 xp in Baldur's Gate, for example. In the PC game Gothic 2, the reward could be 3 times that. Reward players for actually doing things in the adventure, instead of just mindlessly killing.
This is not as radical as it may seem at first. Tournament adventures are scored in a similar manner. Why not transplant that into an actual game?
So, I propose this system, scaled to D&D:
EXPERIENCE
You get experience from two broad categories. The first is a larger experience award, the major objective. The major objective is the whole point of the adventure. You might get 1,000 points for it.
- Exploring the Unknown
- Investigating an Evil Outpost
- Removing the effects of an evil curse
- Recovering Ruins
- Eradicating a force of raiding goblins
- Destroying an Ancient Evil
- Fulfilling a Quest
- Escaping From Enemies
- Rescuing Prisoners
- Finding a Lost Race
The minor objectives are things that you did during the adventure. They're worth anywhere from 100-500 points, though not more than 300 points should be given unless the objectives took more than one session to complete.
- Following a trail of clues to the next part of the adventure
- Searching around a town's taverns to find a guide
- Bribing a guard (or quietly rendering him unconscious) to gain entry
- Killing or overcoming a monster that is preventing the Heroes from progressing further.
- Using a Magic Portal to go someplace (or come back, or both)
- Travel to a shrine that has been lost for ages, in order to remove the curse.
These are base Experience Awards, and they increase as the Heroes rise in level. A good rule of thumb is to multiply the awards by the Heroes' level. So if the Heroes are 3rd level, they might net 600 X.P. for the last group of monsters they killed. Or, after exploring the ruins to find the foozle they might get 3,000 X.P.
Obviously, you can increase or decrease the base experience award as you see fit. A slower progression might see 500 for a major objective, or even 250! You might even flatten the rate, so even at 5th level the PCs are getting the same amount of X.P. as they did at 1st level. Part of the advantage of this system is the sheer control. You can tailor it to the exact number of adventures you want your players to go through before they level. Also, set up this way, hack and slash actions are not rewarded unless you want them to be.
Showing posts with label d20. Show all posts
Showing posts with label d20. Show all posts
Thursday, May 5, 2011
Sunday, November 14, 2010
Race As Class
Because I love the occasional hot-button topic, I'll be weighing in on the "race as class" debate. For those of you unfamiliar with the debate, there are two schools of thought in the D&D community:
One favors the idea of "race as class," that is, if you're a non-human such as a dwarf or an elf, your character type is automatically accounted for and the ability to fight or cast spells is a racial ability. There is no selection of Elven thief, as you are automatically either a mage or a warrior.
Another favors selection of race and class. That is, you can take a Dwarven Cleric, you're not automatically a warrior-type simply because you chose to play a Dwarf. This would be the more familiar type to modern day players.
We will now contrast how the various editions handle races and classes:
OD&D
The LBBs (little brown books) seem to indicate that if you were one of the non-human races, then you were already in a "class:"
D&D (Holmes Blue Book)
In Eric Holmes' edition of Dungeons & Dragons (blue book, cover by David C. Sutherland III), the trend of using race as class appears to continue. I say *appears* because the one reference to race on page 7 reads: "the four basic classes and races (human, elven, dwarven, halflingish)..." But the classes and races are all lumped together in the experience tables, and page 6 says "any human character can be a fighting man and all halflings and dwarves are members of the fighter class, unless they opt to be thieves."
The terms "class" and "race" are not defined. There is a third way Holmes refers to characters, and that is "character type" (page 7), indicating class and race, which perhaps is the term that should have been used in later editions.
AD&D1e
AD&D hardcover Player's Handbook, first edition, is the first clear delineation between class and race. There you can be one of quite a few races, and you first select your race, then you select your class. There's also quite a bit of fiddly bits that make little sense, like level limits for non-humans. But this has been torn apart in many, many magazine articles, so we won't tackle this here. The interesting thing about the classes is that they now had "minimum ability scores" that you had to roll to be certain classes (like the Paladin). If you didn't roll it, you had no chance to be that class.
Basic/Expert D&D (Moldvay) & BECMI (Mentzer)
The simple race as class structure can be seen here, hearkening back to the LBBs and Holmes. The trend continued in Mentzer's BECMI. In contrast to AD&D, Moldvay had a "prime requisite," which meant the highest ability score you had was used to help determine class selection.
AD&D2e
AD&D2e was, for the most part, a cleaned up revised version of AD&D1e, and the final nail in the coffin for any royalties Gygax might have received. Race and Class are separate entities, and for the most part resemble their 1e counterparts. The main difference was in the fantastic settings created for 2e, introduced "Kits" which could be special classes designed for a specific race (like Elven BladeSinger or Dwarven Chanter).
D&D 3.X
The 3.X naming convention is strange, since its simplified ability bonus tables remind one of B/X or BECMI, but Race and Class are distinct and separate, like AD&D. Eventually 3.X would ape 2e by doing "racial kits" (like the Dwarven BattleRager). Dropping the "Advanced" moniker sent a clear message that this was the only Dungeons & Dragons we would see from WotC, and that B/X and BECMI were effectively unsupported.
D&D 4.X
Does the same thing as 3.X, races and classes are discrete groups, and one must select a race and a class.
My take:
I never had a problem with "race as class" because I'm aware of one of the dictionary definitions. From Dictionary.com:
27. to place or arrange in a class; classify: to class justice with wisdom.
28. to take or have a place in a particular class: those who class as believers.
The word comes from the Latin "classis," which meant class, fleet, division, army, etc. So we can infer that the D&D "class" is merely a grouping, and the only thing in the dictionary that implies profession is class as social standing or caste, hardly an ironclad case. So the snarkiness that I have observed (and been the target of) could have been avoided simply by cracking a dictionary.
Do I prefer race as class? For some things it works well. It gels nicely with the simplified structure of B/X. In the "clone" I'm working on, I have them separate as of this writing, though I'm thinking of leaning toward the race as class model and giving them different "builds" for race-specific classes. Time will tell...
One favors the idea of "race as class," that is, if you're a non-human such as a dwarf or an elf, your character type is automatically accounted for and the ability to fight or cast spells is a racial ability. There is no selection of Elven thief, as you are automatically either a mage or a warrior.
Another favors selection of race and class. That is, you can take a Dwarven Cleric, you're not automatically a warrior-type simply because you chose to play a Dwarf. This would be the more familiar type to modern day players.
We will now contrast how the various editions handle races and classes:
OD&D
The LBBs (little brown books) seem to indicate that if you were one of the non-human races, then you were already in a "class:"
There are three (3) main classes of characters:It is interesting to note that OD&D never defines the term "class." The LBBs also do not use the term "race." The only idea of race that creeps in is that the non-human player's choice plays differently depending on whether you select Elf or Dwarf, and the Dwarf has a level limitation.
Fighting-Men
Magic-Users
Clerics
Fighting Men includes the characters of elves and dwarves and even hobbits. Magic-Users includes only men and elves. Clerics are limited to men only. All non-human players are restricted in some aspects and gifted in others. This will be dealt with in the paragraphs pertaining to each non-human type.
D&D (Holmes Blue Book)
In Eric Holmes' edition of Dungeons & Dragons (blue book, cover by David C. Sutherland III), the trend of using race as class appears to continue. I say *appears* because the one reference to race on page 7 reads: "the four basic classes and races (human, elven, dwarven, halflingish)..." But the classes and races are all lumped together in the experience tables, and page 6 says "any human character can be a fighting man and all halflings and dwarves are members of the fighter class, unless they opt to be thieves."
The terms "class" and "race" are not defined. There is a third way Holmes refers to characters, and that is "character type" (page 7), indicating class and race, which perhaps is the term that should have been used in later editions.
AD&D1e
AD&D hardcover Player's Handbook, first edition, is the first clear delineation between class and race. There you can be one of quite a few races, and you first select your race, then you select your class. There's also quite a bit of fiddly bits that make little sense, like level limits for non-humans. But this has been torn apart in many, many magazine articles, so we won't tackle this here. The interesting thing about the classes is that they now had "minimum ability scores" that you had to roll to be certain classes (like the Paladin). If you didn't roll it, you had no chance to be that class.
Basic/Expert D&D (Moldvay) & BECMI (Mentzer)
The simple race as class structure can be seen here, hearkening back to the LBBs and Holmes. The trend continued in Mentzer's BECMI. In contrast to AD&D, Moldvay had a "prime requisite," which meant the highest ability score you had was used to help determine class selection.
AD&D2e
AD&D2e was, for the most part, a cleaned up revised version of AD&D1e, and the final nail in the coffin for any royalties Gygax might have received. Race and Class are separate entities, and for the most part resemble their 1e counterparts. The main difference was in the fantastic settings created for 2e, introduced "Kits" which could be special classes designed for a specific race (like Elven BladeSinger or Dwarven Chanter).
D&D 3.X
The 3.X naming convention is strange, since its simplified ability bonus tables remind one of B/X or BECMI, but Race and Class are distinct and separate, like AD&D. Eventually 3.X would ape 2e by doing "racial kits" (like the Dwarven BattleRager). Dropping the "Advanced" moniker sent a clear message that this was the only Dungeons & Dragons we would see from WotC, and that B/X and BECMI were effectively unsupported.
D&D 4.X
Does the same thing as 3.X, races and classes are discrete groups, and one must select a race and a class.
My take:
I never had a problem with "race as class" because I'm aware of one of the dictionary definitions. From Dictionary.com:
27. to place or arrange in a class; classify: to class justice with wisdom.
28. to take or have a place in a particular class: those who class as believers.
The word comes from the Latin "classis," which meant class, fleet, division, army, etc. So we can infer that the D&D "class" is merely a grouping, and the only thing in the dictionary that implies profession is class as social standing or caste, hardly an ironclad case. So the snarkiness that I have observed (and been the target of) could have been avoided simply by cracking a dictionary.
Do I prefer race as class? For some things it works well. It gels nicely with the simplified structure of B/X. In the "clone" I'm working on, I have them separate as of this writing, though I'm thinking of leaning toward the race as class model and giving them different "builds" for race-specific classes. Time will tell...
Subscribe to:
Posts (Atom)