Quote Originally Posted by Shirobi View Post
Not for bard. You can easily get two procs back to back. If you could stop a hard cast, fire off a proc then go right back into hardcasting, its not gonna be a dps loss. Not to sound like a broke record, but since I keep getting the same replies, look at how things worked in 2.3 or earlier WoW. Thats the same system we have going here, and there is a reason people used stopcast and addons to give them a view of when the cast had areached the "point of no return" as it were so they could stop cast and begin another one.
Even for bard, the chances of you getting a back to back proc is extremely rare. When you do, if you stopcast macro assuming it exists, to hit your BL proc and it procs again, the mental recognition time to realize you have gotten a proc while your next ability is casting, interrupt it and then recognize the second proc and hit it again would delay your next on-gcd attack anyway, resulting in a loss.

In wow, no good dps player interrupted casts for procs unless it was something that would refresh a very, very important buff. Every guide I ever read and every advice I ever got from stellar players in that game was if you have started a cast and didn't notice your proc, or if a proc happened in the middle of your cast, just let the cast finish. Stopcast macros were basically used for CS/shear or other ranged interrupts. That I could see being useful, a stopcast macro for say head graze/blunt arrow. Don't use a stopcast for procs.