Chaosmancer
Legend
Since i put almost no stock in the various white room, guides etc... Nope... Cannot point you to those for your fix of others agree-ism.
I am one of those crazy types who thinks power and value comes from the intersection of capability and need so i really dont give a rats ass about how other people value x vs y vs z in their games (as far as it relating to mine) and have even less of a concern about white room warriors of excel.
If you want references to how powerful someone else think this feat is, as opposed to how powerful it is actually in your own game, somewhere back in this thrwad a poster who seems to be running in a game whose particulars practically makes the other benefits of SM trivial iirc said it got close to sharpshooter and the great weapon one (the 5/10s iirc) on what we have to assume was the strength of the pre-shove down alone.
But if your position is that its a mid-road not used for power type builds feat and that all this rage has nothing to do with losing a powerful option cuz you know the ones focused on power would not get near the meh, thats fine. Feel free to support that position or whatever.
I know we all can point to many cases where we see such furor and rage over already mediocre options being made more mediocre - likely those drowning out the few quiet peaceful whispers when a powerful option gets nerfed, right?
Ok, but you realize that by your definition of power and value coming from "how powerful is it in the situation that is the game you are playing in"... that all options are "Potent Build Tools"?
I mean, I would be really hard pressed to think of an option that could not be powerful in the specific contest of a game and or party, so your dismissiveness towards the people getting upset makes even less sense.
Honestly, if you believe all options can be powerful, then you can't really decide that people are only upset because they are losing a powerful option. Any option would be powerful, so losing anything would make them upset. If you want to defend your position because some people give more weight to certain options than you feel is necessary, then you also have to acknowledge that many of those people who give that weight were not giving that weight to Shield Master.
I mean, maybe you can be dismissive and inclusive at the same time, but I would find that a very hard position to keep.
"but a lot of us don't really end up parsing our game rules like computer code, so we don't care as much about the exact ordering of events. As long as it works and people have fun that's all that really matters."
Absolutely. As i have said many times, i do not see house rules as second class to RAW, in fact, i put them higher on the pecking order cuz they apply to an actual game in play, to fit that group and setting etc. RAW are built as tools for a generic framework and may or may not suit that group/setting - especially down to the parsed terms level.
Thats why i have advised many time to house rule it as opposed to trying to twist and contort RAW around to skirt or discredit the ruling when you dont like a ruling.
Its easier to house rule to add "after any attack in the action" or even "before or after any attack in the action" to SM in your game, rather than start inventing a difference between "declare action" and "do action" to allow the extra benefits of "do" without the doing.
But some folks rather go with the parsing word war shield for their own purposes
Okay, can I just ask something first. Why do you keep quoting people with quotation marks instead of the quote function? I've noticed it dozens of times in this thread and I can't help but wonder what the purpose is. If you want to respond to something I said but don't want people to know I said it... why even bother with the quotes?
Onto Houserules.
I agree with you. I also have no problem with houserules and don't see them as "lesser rules" in any way. However, I don't think people are twisting and turning the rules language because they need a RAW justification for their rules.
There is no way to debate this ruling in terms of "are we limiting the abuse of an ability" because there is zero evidence that using Shield Master to knock an enemy prone first was abusive of the rules. As we were discussing earlier, this was not an option that topped the charts or even got talked about a lot before this ruling.
However, some of the rules language being used to justify this clarification on Shield Master may have larger consequences for the game. For example, this idea of indivisible actions that can be divided by bonus actions unless the bonus action says it cannot divide the action. This is confusing and concerning if it ends up becoming the default accepted way of looking at the game. It also may inform future design decisions and thus is important for us to figure out.
Plus, let us be honest here, a lot of people who get on the Internet to talk DnD love arguing semantics. We have an excessive number of highly educated people in fields that require that type of thinking, and it breeds a certain atmosphere around the game.
Further, JC's reasons for his volte face are absurd: Shield Master knocking prone being 'cheese'(!!!), and 'Actions cannot be nested' despite the many, many legal nesting of Actions within the rules.
I think that nested action thing is becoming a real sticking point for me. There are more bonus actions that can be taken within an attack action than there are bonus actions that cannot. When the specific rule outnumbers the general rule by that large of margin, you may be looking at the wrong general rule.