The working title is Super Adventures, but that’s kind of blah. Any thoughts?
I’m getting pretty close to being able to publish a first draft, btw.

Tales of the Rambling Bumblers
an RPG blog
The working title is Super Adventures, but that’s kind of blah. Any thoughts?
I’m getting pretty close to being able to publish a first draft, btw.
International Hobo – Your BrainHex Class is Seeker-Mastermind

Your BrainHex Class is Seeker.
Your BrainHex Class Your BrainHex Sub-Class is Seeker-Mastermind.
You like finding strange and wonderful things or finding familiar things as well as solving puzzles and devising strategies.
Each BrainHex Class also has an Exception, which describes what you dislike about playing games. Your Exceptions are:
» No Fear: You do not enjoy feeling afraid, preferring to feel safe or in control.
» No Punishment: You dislike struggling to overcome seemingly impossible challenges, and repeating the same task over and over again.Learn more about your classes and exceptions at BrainHex.com.
Your scores for each of the classes in this test were as follows:
Seeker: 19
Mastermind: 16
Socialiser: 15
Achiever: 8
Daredevil: 7
Survivor: 0
Conqueror: -6Go to BrainHex.com to learn more about this player model, and the neurobiological research behind it.
Feel free to take a copy of your BrainHex icon and display it anywhere you wish! Simply right click and choose “save as”. All we ask is you provide a link to BrainHex.com anywhere you use our images.
Thanks for taking part in the BrainHex survey!

In Pricing breadth in skills, T-Bone, of the Games Diner, muses on how to price depth vs breadth in skills:
Games typically address depth in all the detail you’d want – which isn’t much, really. Some systems might offer skills as a binary “you got it or you don’t” switch, which won’t satisfy enthusiastic character designers. Most systems are more accommodating, with the ability to purchase a desired level of skill. Nothing fancy is needed; just by picking a level, players can make the character a laughable novice or an awesome master, or anything in between, where Astronomy or Knife Throwing is concerned. All fine and good.
Breadth, though, isn’t something you’ll see addressed with such a freely-set measure. A system will pre-package the breadth of skills, establishing that combat skills consist of Sword and Knife and Shield and so on, and scientific skills consist of Astronomy and Chemistry and Physics and what not. There may be limited options to tweak breadth, such as ways to learn smaller subsets of those skills, or to lump them into broader Hand Weapon or Science skills. But they’re typically coarse tools.
This neglects one very common and workable approach, perhaps because it shows up mostly in systems on the rules-light end of the spectrum, which is to have everything cost the same but let the player define the breadth of the skill when purchased and assume there’s some GM-guided ad-hoc trade-off between depth and breadth in use. E.g. if you define your skill as Science a successful roll will give you somewhat less information identifying an alien disease than if you had defined it as Xenobiology. Roughly equivalently the target number can be set higher for a really broad skill than a broad skill than a narrow skill than a super-specialized skill. I find this works quite well in practice, because the GM is already making those kind of judgment calls when setting target numbers or deciding what to tell the player when a knowledge skill is employed. Even if you did as T-Bone suggested and had a detailed list with a complicated formula for figuring cost, the GM would still have to make the same sorts of judgment calls as to whether the more or less specific version applied and where to divide the skills.
There are actually two kinds of sets of skills to consider when you think about grouping them: skills that can be arranged in a hierarchy of specialization, and skills that are discrete even if similar. Knowledge skills are often hierarchical. Science -> Biology -> Xenobiology -> Xenoforensics would be an example of increasing specialization in a single category. Performance skills, such as languages or musical instruments, are related but discrete. French and German aren’t really specializations of general training in “European Languages”, nor are cello and violin specializations of the broader skill stringed instruments. Facility in one might make it easier to learn another, and it’s possible to have a general aptitude for being good at learning things in the category (having an “ear for languages”), but it doesn’t really make sense to have a skill rating in Languages without skill at any particular language unless it’s just a placeholder indicating that if you ever do learn a language it will be easier.
Discrete but similar skills probably do require some way of assigning a cost along the lines that T-Bone discusses, where there are increasing returns on investment, or you’ll end up making perfectly logical characters of a sort who actually exist in the real world prohibitively hard to create in the game system. His particular ideas (basing the cost on the square root of the number of discrete skills, or on a sequence where each additional skill costs half what the previous one cost) are, imo, too complex and almost immediately run into problems of fractional costs, but it would be possible to fix that by doing the inverse: instead of saying the first language costs 1, the second 0.5, the third 0.25 and so on say you have to spend 1 at a time, but each 1 gives you an additional number of languages equal to double the prior step: for 1 you get one, another 1 would add two more, another 1 would grant you four on top of that, and so forth. Even simpler would be to do something like: one, two, three, many. That is, make the character pay for the first three, and have the fourth step jump to however many the player likes. These kinds of skills are almost never the focus of the game, and not only does the marginal utility of an additional skill itself drop off quickly, so does the utility of tracking exactly which ones are known. I’d rather the player be able to say “My character knows all the goblin and giant tongues” and move on than have the game stop while everybody looks at their character sheets to see if a particular dialect is listed.
Rob Lang, of the Free RPG Blog, has switched sides of the GM’s screen and asks for tips on becoming a better player, so here are some of my thoughts:
Ultimately, most of this advice boils down to a principle of courtesy. Keep in mind that everybody at the table shares the responsibility of making the game fun and entertaining for everybody involved. Be willing to make sacrifices as far as what would be your ideal ultimate solo gaming experience in order to keep everybody involved and having a good time. Be flexible in what and how you play, and don’t play if you’re not having fun.
Based on some of the comments on my post on Super-Simple Combat Maneuvers, some people are looking for more crunch to the system, or at least a more reliable way of forcing the issue. Here are some possible added fillips, bearing in mind that to the extent that you make maneuvers a more attractive option than just doing damage you tilt the combat towards being resolved by the use of applicable maneuvers instead. The original rules were designed so that you probably couldn’t use them to win a combat you would otherwise lose, at least not without a big dollop of luck. The result, though, was that you probably wouldn’t bother to employ them unless circumstances gave you a specific reason to (we don’t need to defeat all these enemies if we can just get the MacGuffin to the Altar of Doom); it gave you a nice way of adjudicating attempts to do things outside the scope of the normal roll to hit/roll for damage/rinse and repeat cycle of combat, but it deliberately didn’t give you a lot of incentive to do so or choices to make in how to go about it.
If that’s not adequate, then here are some optional rules to try:
The exact numbers would vary depending on the system being used (a +/-1 is a lot bigger deal in Savage Worlds than in a d20 system) and the feel you’re going for. You probably wouldn’t use all of these unless you wanted a very maneuver-centric game, and you should be prepared to tweak the exact numbers or even which ones you’re employing depending on how they work out in actual play.
Of these, I think I like Upping the Stakes the best. There’s something conceptually kind of nice about the idea that you can press for extra damage, but you have to leave a way for the defender to weasel out of it if they value their hide more than whatever the tactical disadvantage might be.
As far as my actual play goes, it’s too early to tell. Friday we only had one combat, and it was pretty much a straight-up hackfest, as the party fought off a group of Neanderthals. Nobody tried anything fancy except for one wimpy mage who tried playing dead. There was one PC death to a nasty crit, but nobody expected Expendable 1401 (yes, that was his name) to last more than a session or two in the first place.

I’m a fan of players being able to do more things in combat than just tick off damage against opponents. Things like disarming, tripping, forcing the opponent to yield ground, binding their weapon and so forth add a lot to the feel of combat and the tactical options. I’m not a big fan of most of the rules that I’ve seen to do things like this, including various rules I’ve come up with over the years, because they either add too much complexity or accomplish too much or too little, or both. Sometimes certain maneuvers become surreally effective, particularly if you’ve optimized your character; other times there’s no point in trying: you’re strictly better off just hacking away, and the heck with flavor. It’s hard to strike a balance, particularly if you’re concerned with not just whether the combat mini-game has no clear dominant strategy but whether the results seem plausible and entertaining for the kind of genre you’re playing.
I think, though, I’ve come up with a solution that finesses most of these problems nicely, and can be bolted on to a wide variety of systems and genres. I give you Super-Simple Combat Maneuvers:
That’s all there is to it.
So why would a defender choose to take the effect, rather than the damage? Well, because it seems like a better option at the time. It’s going to be hard to push somebody back into a bubbling pool of lava, or make them drop their only weapon, but it’s not impossible (thanks to the crit=success rule) and a lot of the time it may beat taking damage. In systems, like D&D at higher levels, where a character can take dozens of hits before being in trouble you may have to wear them down a while before this sort of maneuvering for advantage starts to have bite…but that’s a feature of being able to take oodles of hits. If you allowed maneuvers to be a cheap way around that, then you would lead straight into the kind of balance problems this is designed to avoid. To the extent that you’re satisfied with characters being able to shrug off hits, you should probably be satisfied with them shrugging off other combat effects–at least until they start to be worried about taking the sword-blow to the arm instead of dropping their weapon.
In more lethal games, it should be a big temptation to go with the maneuver instead of toughing it out, particularly if doing so doesn’t obviously equal defeat. That puts a premium on maneuvering when you have a cunning plan, such as setting somebody up for a flank attack or clearing a path for a comrade, instead of a cheap way to bypass the normal combat procedure.
On the attacker’s part, there’s no real penalty for trying something interesting. The opportunity cost is just losing the chance at whatever the normal critical effect is, plus giving the foe the chance to avoid damage. But presumably you’re attempting the maneuver in the first place because you think that under the circumstances you gain a greater advantage from whatever you’re trying instead of damage from a normal blow. If they agree, then at least you still get your damage…if they don’t, well that’s what makes for tactically interesting decisions.
One nice feature is that there’s very little chance that some clever rules-monkey (hi Doug!) can use this to break your game, at least any worse than it’s already broken, since whereever it might be abusive the defender has the option of defaulting to the regular system. The weak point that I can see is that if “criticals” are too easy to get in the default system then you might have too many battles ending with the defenders pushed off a cliff…but that should be easy enough to tweak (e.g. by require a crit and a “confirmed” crit, with the confirmation roll tailored to exactly how often you think the attacker should be able to force the issue…which depending on your style of play could be never). In the worst-case, you end up using the default combat all the time, but at least it’s cost you no effort or extra complexity.
So what counts as a maneuver? I’m inclined to say that players should feel free to make stuff up as they go, perhaps with GM veto. If players keep trying to shoot guns out of their foes’ hands, a la an old TV Western, that should be taken as a hint that they’re happy with that as a style instead of making it a tug-of-war with the GM over which genre conventions the game adheres to. If they want to try to knock a guard out with one blow as a maneuver, why not? On the other hand, if that’s just too loosey-goosey for your play style, perhaps because you worry that in pursuit of momentary tactical advantage or even humor, you all might try too many things that undermine the feel you’re going for, it would be simple enough to make a list of the “standard” maneuvers such as
I’m going to add this to our game tonight. I’ll report back on how it goes.
Advanced Gaming & Theory: Handedness?
Sometimes it can be helpful to a dungeon master for a character to have a favored hand written on his character sheet. This can quickly solve some arguments which might pop up over throwing stuff while still armed, as well as some odds and ends.
Now, we both know that if we just let characters specify what hand they favor, then they will always claim to be ambidextrous, which we just can’t have. That and I love charts that allow us to use our poor and often neglected 12-sider.Roll—Handedness
1-9—Right Handed
10-11—Left Handed
12—Ambidextrous
Personally, I like rules that are easy enough to remember that you don’t even need a chart, so in my work-in-progress system you roll 2d6. On doubles you’re left-handed, on a 12 you’re ambidextrous. That gives results that are quite reasonable, and I can remember it off the top of my head.
I use the same method for determining sexual orientation for NPCs (or PCs that want to roll). That probably overstates the prevalence, but re-using a rule is even easier than remembering a new one!

The Dice Bag complains about the number of rolls needed to generate random encounters:
I have always enjoyed the fact that both as a player and a GM I’ve never had to suffer the “oh it’s been 10 minutes of game time I must roll some dice to work out what’s going to happen next” moments. Don’t get me wrong the occasional secret skill check by the DM works great but the structured approach to random encounters that most systems encourage is beyond me.
Taking them out completely isn’t an option for me either. I actually like the supposed randomness the idea can give to gaming sessions if you’ll believe that or not. It’s the ‘regular’ rolling of dice I despise as it turns the game into a series of turns. That’s fine when it comes to combat but for general play it’s to much of a hindrance for me at times.
So how did I every get around this part of the mechanics? For a couple of years I had a small computer program that produced a page full of random numbers from whatever dice you chose to roll. I coupled this with maps that had specific points where an encounter ‘roll’ would take place rather than at set times during the game. It did mean that if a group stayed at one point they shouldn’t come across any enemy until they moved off if they had already encountered something whilst there but these were flaws I was willing to live with.
The obvious solution is don’t roll each turn (or whatever the unit) for a random encounter–roll to see how many turns until the next random encounter. This means that, unlike the system he was using for pre-rolling encounters at certain places, it’s possible that the party will have encounters even when sitting still. For added verisimilitude, they might even have an encounter that shows up during the middle of another encounter if it goes on long enough. While it would be easy enough to devise a formula or spreadsheet that would give you the same frequency and distribution of encounters as most published systems, that’s probably overkill. Just pick a die size that gives you an average time between encounters that seems reasonable, and roll it open-ended (if you roll the highest possible on the die, reroll and add). The open-ended roll means the players can’t use metagame reasoning that since it’s been five turns since an encounter they’re due one on the next turn, but it changes the average roll very little.
This is the reverse of my tip to reduce bookkeeping for things such as supply rules. In general, you can trade off die rolls versus bookkeeping. If you feel you’re rolling too often, substitute bookkeeping by rolling to see when the next “event” is and just track time until then; if tracking too many things is getting you down, abstract it as a periodic die-roll to see if a condition has changed by now. I think “time until” works particularly well for events that would otherwise be rare enough that there’s no point in rolling for them, and when you’re using something you’re probably already tracking (such as time). I think “don’t count, roll” works better for things where you’re only tracking for one purpose, and you don’t actually care what the value is until a lot of steps towards a critical threshold have been passed (e.g. individual ammo).
Randomized initiative is a hold-over from wargaming that I’ve never particularly cottoned to. Originally D&D didn’t even have it. Turn order wasn’t even specified, leaving it up to the referee to figure out. I’m sure Chainmail had rules, but the d20 vs. AC “alternate” system that was in the books which everybody actually used made no mention of it. Basic D&D officially had turn order alternating between the two sides, players and NPCs. In that context it made perfect sense to roll at the beginning of combat to see who went first. For some reason, though (at least by the time of the Mentzer Basic D&D) the rules called for rolling each round, which had the bizarre property that a side might go twice in a row. Unfortunately, strict alternation by sides is a) very “gamey” feeling, b) can convey a huge advantage to the side that goes first, or the side that goes twice in a row, leading to a lot of combats where one side or the other doesn’t even get a chance to react before being defeated, and c) doesn’t leave much room for having one character being noticeably faster than another (though Zombies did always lose initiative, no roll needed). Individual initiative feels more natural, and gives a much more fluid feel to combat resolution, allowing characters to react to changing battlefield conditions–perhaps unrealistically so, but a much better fit for adventure fiction. Oddly, to my mind, many systems with individual initiative rules nevertheless include a large, even overwhelming, random component. That puzzles me because it still feels very much like a game, and it inevitably leads to layers of extra complication to try to shoehorn character ability back in…plus slowing play down with extra die rolls and modifiers to arrive at a result that is arguably much less true to either reality or genre fiction. I grudgingly use Savage Worlds’ random initiative system when I run that, in part because the Edges that represent one character being quicker are fairly substantial, but in all my own games turn order goes strictly by the character’s speed. Usually that’s Dex or the equivalent. I’ve toyed with using Int (to represent “quick thinking”) and even incorporated it into a game once…but nobody who’s spent much time around my friend Russell–who is quite literally one of the smartest people on the planet–can take the notion of a strong correlation between brains and fast reaction time seriously. It’s probably better to represent quick thinking as taking some specific advantage (along the lines of and Edge or Feat) regardless of attributes.
Over at Unofficial Games: Murder gets boring, Zzarchov writes:
This one deals with the problem of wholesale slaughter of your enemies. In this particular post I’ll deal with murdering opposing villains, the big villain or at least the stalwart dark lieutenant. Many GM’s are frustrated that they cannot have a recurring villain because PC’s will not stop until they murder them. Its like a party of Terminators.
This is a mechanically based flaw. You either get the same XP for killing, or its the only way you get killing added to the fact that dead villains can’t trouble you later.
I disagree. In my experience, this is a story-based flaw, not a mechanical one. Players will make sure that villains, particularly major villains, are truly most completely dead even in games where there’s full XP for defeating a villain without killing him, and even in games where there is no character advancement at all. What players are really interested in is that dead villains can’t trouble you later; tweaking the XP awards so that they have a reason to “farm” the villain for XP isn’t likely to work, particularly on any players that take the distinction between in-character and out-of-character motivation at all seriously.
GMs compound this situation by “teaching” the players that if they show any mercy towards villains the villain will return again later and only be stopped once something dear to the PCs has been destroyed (The Joker Syndrome) . If you want a recurring villain, you have to think harder about what’s in it for the players and the PCs. Some possible answers:
In any event, as the GM what you should be thinking about is why do you want a recurring villain in the first place? What do the players and PCs get out of it? If the answer is just a bonus to XP if they play it right, you probably need to do some more thinking. Recurring villains work best when the stakes aren’t life-or-death, and when you can keep the players from feeling “I…have had…enough…of you!” Recurring characters are a lot easer than recurring villains in most genres, and I think you can generally get a lot more mileage out of former enemies, now rivals or allies (but are they really trustworthy? dun-dun-DUN) than having the villains all “Keep the money. Use it to buy a funeral. It doesn’t matter where you go… or how far you fly, I will hunt you down… and the last thing you see will be my blade.” unless you want the PCs to go emulating Mal Reynolds.