Still worse, since you don't know how low you rolled. If you get a 11 on an attack and miss, but you have a bardic inspiration and you know a 14 hit last round, you can safely assume that your chance of success is reasonable, while the inspiration would be wasted if you rolled 7. It just takes away from the strategic nature of the game.
Well, yes, more precise information is always going to make your decisions easier, so of course less makes it harder. That's not necessarily a bad thing though; perhaps your DM is just running the kind of game where you need to make those calls based off something diagetic to the game, like their combat descriptions ("You shoot the orc square in the chest but the arrow shatters harmlessly on his armor!") or monster research or something. Or perhaps it's the kind of game that thrives on drama, and you just gotta take your shots sometimes and let the dice fall where they may.
And yeah, theoretically it feels bad to waste a buff on an enemy you'd never be able to actually hit, but because you don't know the numbers, you don't know you could never hit. You're faced with a big scary monster, you try to hit it and can't, you run away. The arc of that encounter is the same regardless of which abilities you used. It only becomes relevant if the DM decides to hit you with another encounter, which presumably they only do if they think your lacking-that-ability would make for another exciting narrative moment. In which case, you'd only be screwing yourself out of that dramatic moment if you'd conserved your ability. It all just depends on what kind of game you're at, whether it prioritizes the gamist mechanical rewards or the narratavist dramatic rewards.
Likewise, sometimes you're going to "waste" your buff on some overkill, but you won't know that either; you'll simply be told "Bardman McBardo's inspiring music gives you the vigor you need to waste that guy" and get to feel good about winning your encounter. The emotions average out.
Yeah. But I'm really not a big fan of that. The strategic nature is a part of DnD. If you remove that you end up making it less engaging, since you just shoot sh*t into the abyss, hoping it might do something, or not. Thats not particularly fun to me.
Not knowing things is interesting, because you can figure them out, or have to plan and think to work around what you know and don't know.
It just feels... pointless if you never understand what's going on and also have no way of figuring it out. You just go somewhere vague, do something vague and accomplish something vague.
That may be fun for some people but its not what DnD was designed for or what I hope to get out of my games. Thats why I also don't recommend using it in every game as a general rule.
Different strokes for different folks. And I'd be very careful about using assumptions of "what DnD was designed for" as a guide for how everyone ought to play now. To quote Terry Pratchett by way of Captain Carrot, "Gold and muck come out of the same shaft." It's more important to understand what kinds of fun your game can deliver on, and how, so that you can tune it for the maximum enjoyment of your table, than it is to determine in the abstract how it "should" be played.
Right. I correct: It’s not what 5e is best used for.
For the rest: That’s what I’m saying. From what I picked up (personal opinion) people really don’t like it when they don’t know what’s going on. But each their own. If your table is happy with it, go for it. I’m just advising against using it as a general rule, because some people don’t have much fun when the game goes this way.
Still worse, since you don't know how low you rolled. If you get a 11 on an attack and miss, but you have a bardic inspiration and you know a 14 hit last round, you can safely assume that your chance of success is reasonable, while the inspiration would be wasted if you rolled 7. It just takes away from the strategic nature of the game.
Well, yes, more precise information is always going to make your decisions easier, so of course less makes it harder. That's not necessarily a bad thing though; perhaps your DM is just running the kind of game where you need to make those calls based off something diagetic to the game, like their combat descriptions ("You shoot the orc square in the chest but the arrow shatters harmlessly on his armor!") or monster research or something. Or perhaps it's the kind of game that thrives on drama, and you just gotta take your shots sometimes and let the dice fall where they may.
And yeah, theoretically it feels bad to waste a buff on an enemy you'd never be able to actually hit, but because you don't know the numbers, you don't know you could never hit. You're faced with a big scary monster, you try to hit it and can't, you run away. The arc of that encounter is the same regardless of which abilities you used. It only becomes relevant if the DM decides to hit you with another encounter, which presumably they only do if they think your lacking-that-ability would make for another exciting narrative moment. In which case, you'd only be screwing yourself out of that dramatic moment if you'd conserved your ability. It all just depends on what kind of game you're at, whether it prioritizes the gamist mechanical rewards or the narratavist dramatic rewards.
Likewise, sometimes you're going to "waste" your buff on some overkill, but you won't know that either; you'll simply be told "Bardman McBardo's inspiring music gives you the vigor you need to waste that guy" and get to feel good about winning your encounter. The emotions average out.
Yeah. But I'm really not a big fan of that. The strategic nature is a part of DnD. If you remove that you end up making it less engaging, since you just shoot sh*t into the abyss, hoping it might do something, or not. Thats not particularly fun to me. Not knowing things is interesting, because you can figure them out, or have to plan and think to work around what you know and don't know.
It just feels... pointless if you never understand what's going on and also have no way of figuring it out. You just go somewhere vague, do something vague and accomplish something vague.
That may be fun for some people but its not what DnD was designed for or what I hope to get out of my games. Thats why I also don't recommend using it in every game as a general rule.
Different strokes for different folks. And I'd be very careful about using assumptions of "what DnD was designed for" as a guide for how everyone ought to play now. To quote Terry Pratchett by way of Captain Carrot, "Gold and muck come out of the same shaft." It's more important to understand what kinds of fun your game can deliver on, and how, so that you can tune it for the maximum enjoyment of your table, than it is to determine in the abstract how it "should" be played.
Right. I correct: It’s not what 5e is best used for.
For the rest: That’s what I’m saying. From what I picked up (personal opinion) people really don’t like it when they don’t know what’s going on. But each their own. If your table is happy with it, go for it. I’m just advising against using it as a general rule, because some people don’t have much fun when the game goes this way.