Upgrade your account to a Community Supporter account and remove most of the site ads.
ShortQuests -- individual adventure modules! An all-new collection of digest-sized D&D adventures designed to plug in to your game.

Reply to thread

Message: <blockquote data-quote="delericho" data-source="post: 2408179" data-attributes="member: 22424">The last 2nd Edition campaign I ran, we used the 4d6-drop-lowest method. One player rolled the following: 18-17-16-16-16-16. I was watching at the time, and didn't spot any cheating. Naturally, this was much more powerful than anyone else in the group, an advantage that he then compounded by playing the only multiclass character in the campaign: a half-elf mage/thief.The campaign didn't last terribly long, as about 6 months later 3rd edition came out, but in that time it was clear that the character was much more powerful than any other character in the campaign.Since then, I have always used some variant of point-buy. I don't really like it (in particular, dump stats and identical stats), but it's better than the alternative.My opinion was confirmed in the one and only 3rd edition campaign in which I've been a player. One other player rolled 11-10-14-17-18-18 (I think - I remember the 14, 17 and 2 18's). The DM was an old-school DM from way back, and retained the rule that you could drop one stat by 2 to increase another by 1 (which I first saw in the Red Box, but then it was only the prime requisite that could be increased). Anyway, the player in question chose to drop his 14 to 12, and boost the 17 to 18. And, again, the character was much more powerful than anyone else in the group.(It's worth noting that that latter character's stats were not generated entirely fairly. The player in question was in the habit of picking up the dice and tossing them down again at once. Consequently, they didn't bounce much, and so one good roll was usually followed by another. The 17-18-18 was rolled in this manner. The player, of course, didn't realise he was 'cheating', and I didn't want to make an issue of it.)</blockquote>

Verification