rowyn

Everyone ends up with their own pet peeves in tabletop gaming. One of mine, which has annoyed me since I started gaming 38 years ago, is "character creation choices that require the players to bet on how long the game will last."

Most games are short-lived. I haven't made up as many characters for games that never started as I have for ones that have, but the ratio is probably no better than 1:3. Many games that make it to one session do not get more than one. The campaign that goes on for years is the outlier. Moreover, you never know which you're going to get when you're making up a character. Plans for epic story arc campaigns often die after a few sessions. The game where my character gained the most power, from starting level to finish, was advertised by its GM as 'a half-assed playtest that will peter out after a week or two.' Mirari and Game of October were both intended to be short-term games and both ran for 2-4 years and had more than a hundred sessions each. The only sense in which they were "short term" was that they each ended at the completion of the game's full story arc. ("Just Trust Me", which took several months to finish, was as close as I ever got to running an actual short-but-complete game).

My point: I can tell you many things about a game during character creation, but "how long will it last" is SO not one of them. And yet many games have things which are in place nominally for "character balance" but in practice are only "balanced" if your game is lasts for exactly X sessions. In original AD&D, the nonhuman races generally had stat advantages but in most cases had harsh level caps. If your game didn't last past level 5, the elves and half-orcs were clearly better. If your game lasted to level 18, they were at a vicious, hideous handicap. (If your group actually played with level caps. I don't know anyone who did.)

Most of D&D descendants don't take approaches quite this dramatic, but I still know many systems where you can take a short-term handicap to get a long-term advantage. "Your character is a Quick Learner: pay 10 xp now and get +1 xp per session." Or conversely: "You are a Slow Learner but you've studied hard to get this far: you get an extra 10 xp to spend now but will get -1 xp per session". Sometimes the abilities themselves are like this: "the skill is useless at the starting level but it's great once you've built it up." "This skill starts out great but it doesn't improve at all with experience, unlike other skills." Vampire: the Masquerade did this thing where your max power was entirely determined by your generation. If you didn't buy the lowest possible generation at game start, your character could never become powerful -- but if you did, you had few points left to be competent at the outset.

It's like the designers think "well, you can trade being great now for being great later, that's balanced." Except that I don't know if later exists, and if later does exist, I have no idea how much later there will be. It's like being told "plan for your retirement: you have about a 40% chance of dying tomorrow and a 1% chance of living 2000 years, and we're not going to tell you the odds of the possibilities in between, and no, you can't get a job again later if you don't save enough. GOOD LUCK." Systems like these always make me feel like the game hasn't even started yet and I've already lost.

I usually make the bet that the game will last for years, when some system makes me do it. I don't think I've ever been right.All my games that lasted for years weren't in systems that did this.

That may not be coincidence, come to think of it.

Nothing in particular motivated this, just thinking about game systems. So what are your tabletop peeves or preferences?

[Poll #1809728]

The most popular of the proposed game methods was PBEM/Forum, so my current plan is to go with that. I need to poke at Google Groups again and see if I like it better than Yahoo Groups. The features I value are:

* Easy to use either by email or by forum, and seamless (ie, makes no difference to other users whether your posts and replies were sent via web form or email.)
* Convenient file-upload space
* Convenient image storage space
* Searchable (Yahoo is bad for this; bard_bloom set up a GMail account for archival and search purposes)
* Threading (Yahoo's threading is bad, too, but in theory I'd like good threading.)
* Database: Yahoo Groups has a little database tool, which I like in theory but which, in practice, is a little clunky to maintain.

It looks like Google Groups has all the features but the database one. I'm tempted to try it, given some of the technical glitches we've had with Yahoo. My most common everyday complaint is formating: the angle brackets (>) that denote replied text format wonkily in Yahoo. Google handled it better. A minor aesthetic, granted, but still. Yahoo also suffered from delays in delivering mail, a few outages, and the infamous duplicate message bug -- where every single message sent to the group got sent out ten or twenty or more times. Oy. That may all be in the past now, but the temptation to look at alternatives remains. Also, I don't think Google has banner ads yet.

Anyone have a bias?

One wish-list item would be an *easy* way to filter people out, so that messages would be visible to certain people and not others. The key word here is 'easy'; I don't want an awkward method or one that requires effort for the GM to track.

On a related note: anything which makes bookkeeping easier is a Good Thing. We used the databases to keep track of things like active spells and NPC names (the last is especially handy for those pesky minor NPCs.) The databases were nice when they were up-to-date, but updating them was still an extra step that people had to remember to take. The biggest advantages of the databases over a file was that (a) anyone could update it and (b) no messing with uploading it.

But in my ideal world, some programmed feep would make the database for me, by combing through posts, detecting NPC names and descriptions, and compiling them. :) I could ask for keywords on posts that have certain types of information, like :desc: the first time a character is described, or :name: the first time one gets named, etc. But that's not as useful as a database, and I'm not sure it's enough easier that it'd be worth doing. Also, I can forget to include a keyword as easily as I can forget to update a database. :P

Bard gave out occasional exp bonuses to incentivize players to do bookkeeping, which I thought was rather a nifty way to get work done. But there are still disadvantages to that, not the least of which is 'someone still has to do it'. And bookkeeping can apply to a range of continuity things: GM rulings on the way things work, setting descriptions, object descriptions, plot points, information revealed and who it's revealed to, etc. Anyone else have ideas on how to handle bookkeeping?