The first time Kluzen the Protector selects someone for a mark, it works fine - they get the warning, it strips properly, etc. Any time after the first, the player receives no warning - the first indication they have something is going wrong is getting a message about being hit with his wrath, spreading the incurable curse to anyone around them. I haven't confirmed this, but some people were saying this behavior even persisted through pulls.
This is the same instance/named that the Mental Infestation debuff didn't care about the 12m range thing either. I got hit with it at 30m from him among other ranges.
I can confirm this happened to two of my raiders in an instance which was begun at 8 eastern on Tuesday the 9th.
Chath - The first time he infects it is the mark. Upon "reinfection" it is the wrath. You have the same reaction time after both before the detriment spreads. Miragian - As far as I can tell mental infestation hits everyone and is a ramp-up damage, then drops and ramps again. Maybe you're thinking of Mental Protectorate which is the detriment involved in the OPs post.
Notice it says "within 12m" As you yourself said, it hits *everyone*. Which is not at all like it seems like its meant to work. I assume its meant to be a "Joust out." but, with a range of in at least one instance in excess of 30m, that doesn't work.
Warning message to implementation is too short. Possible solution = center of screen messages instead of chat box "Lost in combat spam" messages.
Yea verily caballeros, relying on nascar message spam screen to warn of a pending 1. 2658 second pending time until raid wide det. is optimism of the highest order. Bold center screen is great suggestion! -the Ayodi
We didn't see the issue last night, but our encounter seemed to bug out and not cast it properly for a majority of the fight, so I'm not sure whether it was just *not* casting it on people a second time instead of making sure it told them they were marked again.
This is feedback and should be posted in the Feedback forums. If you are encountering a separate issue, please create a new thread in the Bug Reports forums if there is not a thread already.