The more I read, play, and think about the B/X rules, the more I find myself undoing the various houserules and “fixes” I’ve implemented over the years. The more I work out what the rules really say and the more I’m able to let go of assumptions brought into B/X from other editions, the better I think the best version of the game keeps getting.
One houserule that I think I’d like to drop but won’t, though, is the ability score generation. Rather than 3d6 in order with a limited 2-for-1 point swap, we go with 4d6 drop lowest and arrange as desired.
Personally, I think 3d6 gives perfectly playable results, and perhaps even BETTER results, in game terms. However, players seem to be universally opposed to in-order rolling and the dejection of players over a few bad rolls really can sour the session.
So 4d6 drop lowest, arrange as desired is it for us. While I may have no issues deciding to go with a fighter instead of a thief because I rolled crappy Dexterity–or I may be perfectly willing to play a thief with crappy Dexterity–many players are not so inclined. I can explain to them all night long that the randomness of the rolls can bring out fun that was not expected, but they’re still going to be pouting because they really wanted to play a thief this time. So arrange as desired and play your thief, gosh darnit.
Same goes for 4d6 drop lowest vs. 3d6. Sure, we all know that 3d6–on average–gives perfectly playable ability scores for a game with power levels like B/X. But telling that to the player who just rolled a 4 and will be suffering a significant mechanical penalty forever just doesn’t work. “But your weak Constitution and reduced hit points will make this a FUN character to roleplay and you can make his fragility a memorable experience!” just isn’t going to cut it with most players most of the time.
So 4d6 drop lowest and arrange as desired might be a sop to the players, but it’s a reasonable one that I’m happy to make. I want my players to want to play B/X.
Of course, this all leads to the “dump stat Charisma” problem. But that’s a post for another day.