bargle0
First Post
D&D suffers a little bit from overloading certain terms (ex: "attack"), but if there is to be any difference between the following triggers...
"When an enemy targets"
"When an enemy attacks"
"When an enemy hits or misses"
"When an enemy damages an ally with an attack"
"When an enemy bloodies an ally with an attack"
All of which are basically used in various ways by different powers...
Then yeah, you should decide a little sooner in the action. Now, a _lot_ of games don't slow things down enough to make that decision before you do "know too much" and really, I'm all for going with whatever plays best at that point.
I think it is telling that they differentiate "targets" from "attacks" and "hits" in triggers. It is very frustrating that they have conflated what they mean by "attack", but I think it's unambiguous in this case.
That being said, people should play Disruptive Strike however they want in private play. In public play, I think the rule is fairly clear. When I run across a DM that likes to do things like roll behind the screen and declare "he hits you!" without declaring an attack first, I try to let him know that I will be interrupting any attack made. I will also have my dice (attack & damage) in my hand with my conditional modifiers already added up to minimize game disruption when I use my immediate attacks.