shadowoflameth
Adventurer
Then it's a problem with backward compatibility. I like feats but not every game uses them. Certainly every background doesn't need a feat or a language.I don’t think feats are going to be optional any more.
Then it's a problem with backward compatibility. I like feats but not every game uses them. Certainly every background doesn't need a feat or a language.I don’t think feats are going to be optional any more.
No need to tie feats to background, just have a character gain a feat at 1st level.Then it's a problem with backward compatibility. I like feats but not every game uses them. Certainly every background doesn't need a feat or a language.
The whole kerfuffle started when people pointed out that the backgrounds in the playtest were using some of the same bias (intended or not) that racial cultures did. Gladiator (with its strength boost, orc language and SAVAGE attacker feat) was viewed as WotC saying gladiators in D&D were associated with orcs and savagery, and that just is the old orc lore with extra steps. There were threads on Enworld pointing this out, lest you think this was just a Twitter outrage. People literally read it and thought "why do all gladiators speak orc? Why do all farmers speak halfling?" And a few wondered why all criminals are dexterous or nobles charismatic. In short, people read it as "this is what a gladiator/farmer/noble is" rather than "this is what they could be".Again, I’m not seeing the issue. Everyone is concerned about hypothetical players who might think the examples aren the only options, but no one seems to actually think that.
It started because WotC are again writing things backwards.The whole kerfuffle started when people pointed out that the backgrounds in the playtest were using some of the same bias (intended or not) that racial cultures did. Gladiator (with its strength boost, orc language and SAVAGE attacker feat) was viewed as WotC saying gladiators in D&D were associated with orcs and savagery, and that just is the old orc lore with extra steps. There were threads on Enworld pointing this out, lest you think this was just a Twitter outrage. People literally read it and thought "why do all gladiators speak orc? Why do all farmers speak halfling?" And a few wondered why all criminals are dexterous or nobles charismatic. In short, people read it as "this is what a gladiator/farmer/noble is" rather than "this is what they could be".
The question is whether having these prepackaged bundles few people beyond be players are going to use is worth the chance that a background is viewed as restricting or even problematic. I want to trust WotC can thread that needle, but I've seen how WotC has made some unforced errors and how quickly people were willing to jump on the gladiator thing as yet another example of that. IMHO, the limited value of the premade bundles isn't worth the headache of people analyzing them as world building. There is no language you slot into gladiator that doesn't paint the race as violent, and having "choose x" is a waste of space.
So yeah, people will make that mistake because they already have. And it immediately became a minor tempest in a teapot. And the fixes are to make the system more complicated or redundant. So maybe the best move is to abandon the presets or reword them closer to the quick builds in the class section (a paragraph full of plain language suggestions). But the current format is ripe for misunderstanding.
I expect WotC feels presenting four decision points at the beginning of a section will scare off all those precious new players they're courting.It started because WotC are again writing things backwards.
Backgrounds should be presented 1st as:
1. Pick +2/+1 or +1/+1/+1 for your ASIs
2. Pick any 2 skills
3. Pick any feat
4. Pick your choice of 2 or 3 languages, tools or weapons
Then, and only then you could write some EXAMPLES of backgrounds for new people that might not want to create their own or for maybe general guidance what might show up in certain backgrounds.
if examples start on the same page in next paragraph, that should not be a problem.I expect WotC feels presenting four decision points at the beginning of a section will scare off all those precious new players they're courting.
But that's the thing: THEY DID!It started because WotC are again writing things backwards.
Backgrounds should be presented 1st as:
1. Pick +2/+1 or +1/+1/+1 for your ASIs
2. Pick any 2 skills
3. Pick any feat
4. Pick your choice of 2 or 3 languages, tools or weapons
Then, and only then you could write some EXAMPLES of backgrounds for new people that might not want to create their own or for maybe general guidance what might show up in certain backgrounds.
I think what would scare off new players is the overwhelmingness of having to create your own Background. Having preset examples helps ease new players into the game and gets them started. Then when they have a little experience under their belts, they can try their hands at expressing their creativity by building their own Background.I expect WotC feels presenting four decision points at the beginning of a section will scare off all those precious new players they're courting.
Can't agree with you there. My players don't want to create a background. They just want to pick one and go. So, for my players, I hope they keep backgrounds in '24.I want most of them gone. Write one or two as "how to" illustrations if they must, but ditch the rest so that players stop treating the illustrative examples as proscriptive defaults.
What? That is exactly what they did in the UA. They presented the default as make your own. The examples were just examples. Did you read the UA?It started because WotC are again writing things backwards.
Backgrounds should be presented 1st as:
1. Pick +2/+1 or +1/+1/+1 for your ASIs
2. Pick any 2 skills
3. Pick any feat
4. Pick your choice of 2 or 3 languages, tools or weapons
Then, and only then you could write some EXAMPLES of backgrounds for new people that might not want to create their own or for maybe general guidance what might show up in certain backgrounds.