Even Steven Array

Kurtomatic

First Post
/cue Seinfeld

I've never used arrays for chargen in my past campaigns; my long-time group of players are point-buy hounds. I am now thinking about using them in the future.

As a DM, I like the idea of everyone agreeing to the same array, but that's very unlikely to happen, and I like to give players interesting choices in chargen. So instead I am considering giving them three or so arrays to choose from. I realize that all else being equal, some arrays are more optimal than others, so I will try to offer carrots with the less optimal arrays.

In that vein, a 'generalist' array is the classic unoptimized array pattern, particularly in 4E. So assuming I can balance this with a valuable mechanical perk, what do you think is the minimum (reasonable) primary ability score that an 'Even Steven' array can get away with? Is 15 too low, without being build-specific?

Strictly for the sake of conversation, lets start with 15/14/14/12/11/10. Just how bad does that suck? Is there a useful Even Steven array a resourceful player can work with?
 

log in or register to remove this ad

Personally I feel 15 is too low, 16 is really the minimum starting score to avoid frustrations.

As such, 16, 14, 14, 12, 11, 8 would be a great all around option that doesn't limit feat choices but still runs a playable character.
If you don't want any 8's.....
16, 14, 12, 12, 12, 10 or 16, 13, 13, 13, 12, 10
 


There are two generally accepted arrays:

16,16,13,11,10,8 (or 16,16,12,12,10,8) -- focus on two stats, use your few remaining points to qualify for whatever feats you might want, or to shore up your lowest defense.

... and:

16,14,14,13,10,8 -- focus on one stat, use two others for class abilities and/or feats.

However, I personally have had success with a few other allocations, like:

16,13,13,13,13,9 -- main focus on one ability score, but I needed to qualify for a LOT of feats early on, and I couldn't afford to dump anything except Charisma.

IMHO it's key to put at least 16 in your primary attack stat (before racial mods). If you have class abilities which key off a secondary stat, decide how much you want them. For example, an Eladrin Tactical Warlord would make great use of the 16/16 array (ending up with a 16 Str, 15 Dex, 18 Int and whatever was left in Con, Wis and Cha), while a Dwarf Fighter might prefer the 16/14/14 array (ending up with a 16 Str, 16 Con and 16 Wis).

Those two cases are unusual, though. Most of the time, you'll want an 18 in your primary attack stat (after racial mods).

Cheers, -- N
 




I guess I'm not really sure why you would want to mandate specific arrays or for that matter limit choices to one of the standard arrays.

First all the standard arrays are just legal point buys that they printed in the book to let you get on with it quicker, so there is no fundamental difference between standard point buy and standard array.

Second I don't think it really speeds up character generation much. Maybe it does if you're using CB, but even then most time seems to be spent choosing things and ability scores are only one of a slew of choices you have to make, so its not really going to make things that much faster in my experience.

There are certain builds where it just makes good sense to start with an 18 in a score. Probably MOST characters will benefit from going with a starting 16 (or two), but its not a hard and fast rule. Of course there are going to be those players that are absolutely die hard "You must have an 18 starting primary stat" camp people. Is there a reason to force them to play differently than they would prefer? Seems to me player choice trumps everything unless there's a good argument against it.
 

What level do you plan on starting at and what level do you plan on reaching?

As DM, are you willing to adjust monsters to compensate for low abilities? If so, then making all the PCs have the same array, low or not, would not be a problem.
 

As DM, are you willing to adjust monsters to compensate for low abilities? If so, then making all the PCs have the same array, low or not, would not be a problem.
Absolutely.

4e is designed with very narrow constraints. If the DM is willing to do the work to alter those constraints, then designing for the pre-made monsters & modules is no longer necessary.

Cheers, -- N
 

Remove ads

Top