OptionalRule
Hyperion
Thanks for your reply. I may not have framed it right. I was meaning to say this can be a problem and the article is just for an examination of where design in this case is more likley to cause a problem and why so DMs can think through mitigation strategies....
I haven't really found it to be a problem except, ironically, where Crawford has made some kind of odd, non-binding Sage Advice ruling on an exception, which is, uh, how to put this, um, obviously wrong? Obviously silly? A couple of times a player has been like "apparently it works like this when these conflicting exceptions apply" and quoted Sage Advice, and I've had to be, like, absolutely not, no it doesn't.
Also, you can pretty easily find the worst possible exception stacks just by going to RPGBot and looking at the optimization guides for the class/subclasses the PCs are playing. If there is any particularly obnoxious exception stack, they will have highlighted it there, so you can anticipate it and take whatever action, if any is needed. Usually none is needed, it's just useful to know about it.
...
Lots of people are replying that they just say something and their players accept it and move on. I'm happy for them, but this isn't the case in most of my games.
I enjoy the saying "A problem well described is a problem half solved". I'm just writing down my description of the problem, why it is more likely to occur on DnD and provide some tools to get ahead of it.