This is NOT the same double proc bug as it was on beta, it’s the opposite.
I have 5 points in Reflective Shield, but the talent is not working over 80% of the time.
The talent simply stops working often and randomly. Sometimes a mob will take reflect damage after the first hit or two, then it will stop working. Other times and entire shield will be absorbed without reflecting at all. Sometimes refreshing the shield will get it working again, sometimes it won’t. I can’t figure out a pattern, but it hardly ever procs at all.
Other priests have also noticed the same effect. It completely ruins the discipline tree for me since it was one of the talents I was most looking forward to. Has anyone noticed this and figured out a way to fix it?
1 Like
Bumping this as I’m experiencing the same thing 
1 Like
I’ve tested this a bunch since I love the talent and It is only reflecting 1 or 2 absorbs for the length of the shield. I hope it gets looked at.
2 Likes
Just make sure to report the bug in game as well. Definitely sucks that it’s broken
1 Like
I’m having the exact same issue at the moment. I’m fighting mobs that I get down to like 10% and then trying to wand them down thinking that reflective shield will do the rest of the damage. Only damage showing up is my wand
Sometimes I apply pws, the first 3 swings or so will show minor reflects for 50 dmg and then stops reflecting damage entirely until I spell expires or they break it. Makes the talent absolutely worthless for both pvp and pve.
Answers that question, wanted to ask if it was still bugged.
So crazy that something so game breaking can still be bugged.
Here’s hoping it gets fixed soon. I’m going to submit another bug report and if you haven’t submitted one yet I’d recommend submitting one so this gets looked at sooner rather than later.
Has this been fixed yet? I respecced out of shield since it is taking so long.
Still bugged as of june 30
Good to know, was about to test it again. Gentle reminder to please submit (another?) bug report ticket in game so this can be address or at least acknowledged. Hopefully we’ll get a fix for it soon.
Still broken as of July 12 and no news about it being looked at either
This is still broken as of Aug 19th, this is literally breaking the spec, can we at least get a response??