D&D (2024) If Your Builds Not Online By Level 6 Dont Bother?

Just talking about a “build” raises my heckles.

This is because from this mindset, character abilities are the goal, and they don’t matter to the campaign.

If you are not having fun before your “build comes online”, you are more focused on your character sheet than what is happening at the table.

Instead, focus on reacting to what happens to your character. What is their story? I have had multiple characters re-roll their class or multiclass as a response to a character’s development. I usually help the character be effective with magic items or allow them to change their class.

People generally know what you are talking about though.

I dint generally use power builds just avoid the trash ones.
 

log in or register to remove this ad

... I do let magical solutions work if it makes sense but to take Speak with Dead as an example, how many shows and movies are there where the victim doesn't know who the assailant was? ...
There is a difference here that I highlighted - the player investment in an ability. If you have a warlock that selected the ability to speak with the dead as an invocation, not letting the ability be effective is invalidating that selection. Imagine if your PC took the Crusher feat after you find a +3 Maul ... and the DM then goes on to put only Mighty Servants of Leuk-o (the infamous creature immune to bludgeoning damage) in every combat.

In my experience, when a PC invests in an ability, they want that ability to shine. This is true of feats, subclasses, magic items (whether found or purchased) ... and even spell selection: even for clerics that can change spells easily. If the DM negates that choice to control how the story unfolds, players feel it ... and it is not pleasant. Also, it tends to make the game seem to unfold only as the DM wants it to unfold ... not how the players figure it out.

As I said, the occasional naturally unfolding situation where it absolutely seems like the deceased would not know who their killer was for obvious reasons is fine. However, if the excuse is just that you, as a DM, decided the NPC victim was facing away from the killer - when the killer had no reason to hide their intent as they were isolated and the killer was more powerful and faster ... well, that just seems like DM fiat.

This can be a huge problem. A decade ago I played with a DM that wanted to run the Dark Sun series of modules. Those modules have a huge railroad problem. They do things like dictate what the players response should be when threatened with no room for other responses - if they fight back everyone will be killed and if they try to flee they have to be stopped because the module needs the PCs to do what the threatening NPC wants. It assumes the PCs do it to instead of just fleeing away ... Anyways, I was playing in that game using modern character creation rules that the module did not anticipate and my character had a teleportation ability at low level. This would allow me to do something the module didn't anticipate I could. When I said I was going to teleport and XXXXX to solve the problem the DM stopped the game for about 10 minutes to try to figure out what to do. In the end, he said, "it doesn't work." I asked why and he said, "You don't know." I spent a few moments prodding him before I came to the conclusion that the module was not going to work if I could teleport, and he had no idea why it wouldn't given everything that had taken place.

No moment in 40+ years of D&D has taken me out of the game more than that moment. The story game way to the railroad. I stopped being a player in the game and became an observer where my success and failures were dictated to me, rather than being due to my contribution. We played that game for another year, but it was hard to care when I knew that we were just along for the ride, and the dictated story was only so-so.

That was an extreme case of the phenomena, but players feel that cut every time you say, "No" rather than "Yes, and ..." You get much better results when you let their abilities work as they are designed to do without putting up barriers that are not truly necessary.
 


There is a difference here that I highlighted - the player investment in an ability. If you have a warlock that selected the ability to speak with the dead as an invocation, not letting the ability be effective is invalidating that selection. Imagine if your PC took the Crusher feat after you find a +3 Maul ... and the DM then goes on to put only Mighty Servants of Leuk-o (the infamous creature immune to bludgeoning damage) in every combat.

In my experience, when a PC invests in an ability, they want that ability to shine. This is true of feats, subclasses, magic items (whether found or purchased) ... and even spell selection: even for clerics that can change spells easily. If the DM negates that choice to control how the story unfolds, players feel it ... and it is not pleasant. Also, it tends to make the game seem to unfold only as the DM wants it to unfold ... not how the players figure it out.

As I said, the occasional naturally unfolding situation where it absolutely seems like the deceased would not know who their killer was for obvious reasons is fine. However, if the excuse is just that you, as a DM, decided the NPC victim was facing away from the killer - when the killer had no reason to hide their intent as they were isolated and the killer was more powerful and faster ... well, that just seems like DM fiat.

This can be a huge problem. A decade ago I played with a DM that wanted to run the Dark Sun series of modules. Those modules have a huge railroad problem. They do things like dictate what the players response should be when threatened with no room for other responses - if they fight back everyone will be killed and if they try to flee they have to be stopped because the module needs the PCs to do what the threatening NPC wants. It assumes the PCs do it to instead of just fleeing away ... Anyways, I was playing in that game using modern character creation rules that the module did not anticipate and my character had a teleportation ability at low level. This would allow me to do something the module didn't anticipate I could. When I said I was going to teleport and XXXXX to solve the problem the DM stopped the game for about 10 minutes to try to figure out what to do. In the end, he said, "it doesn't work." I asked why and he said, "You don't know." I spent a few moments prodding him before I came to the conclusion that the module was not going to work if I could teleport, and he had no idea why it wouldn't given everything that had taken place.

No moment in 40+ years of D&D has taken me out of the game more than that moment. The story game way to the railroad. I stopped being a player in the game and became an observer where my success and failures were dictated to me, rather than being due to my contribution. We played that game for another year, but it was hard to care when I knew that we were just along for the ride, and the dictated story was only so-so.

That was an extreme case of the phenomena, but players feel that cut every time you say, "No" rather than "Yes, and ..." You get much better results when you let their abilities work as they are designed to do without putting up barriers that are not truly necessary.
Occasionally that caster that loves fire based spells runs into monsters that are immune to fire. Sometimes speak with dead doesn't work or an area is by an inner sanctum spell for the guy that loves to teleport. If it always happens that's an issue but magic isn't always going to solve every problem. I also use logic - if I think the murderer would know how a speak with dead works, they're going to take precautions.

It's not something I use often and certainly not just to nerf a character ability. I also don't plan things out with specific character strengths and weaknesses in mind so sometimes the murderer is a cleric that knows all about speak with dead. It just depends on the scenario and in-world logic.
 


Remove ads

Top