Cinn
Banned Jerk
Lately I've been lazy and using my Dem's Aliminium Pants to tag mobs with.
When using them to gain general agro on a random target in a hypothetical camp of three mobs, one of three scenarios will unfold.
a) I cast sicken on mobA. All three come. I flop, warrior tags mobB. I stand after mobA and mobC reset. Sicken is still ticking on mobA. I engage and kill mobB while sicken runs it's course. Mobs A and C never re-agro.
b) I cast sicken on mobA. All three come. I flop, warrior tags mobB. I stand after mobA and mobC reset. Sicken is still ticking on mobA. As soon as I stand mobA re-agro's and starts charging at me, bringing mobC with it.
c) I cast sicken on mobA. All three come. I flop, warrior tags mobB. I stand after mobA and mobC reset. Sicken is still ticking on mobA. I engage mobB. Sicken runs its course on mobA. Now, at any random moment mobA has the possibility to re-agro me. It could be when mobB is still at 50%, or it could be 3 minutes after mobB has already been slain. The DoT on mobA will have run it's course long ago, but for whatever reason I still remain on it's hate list.
---
Obviously scenario A isnt a probblem, and scenario B? well, I assume thats how game mechanics are supposed to work to begin with. Scenario C on the otherhand has caused some pretty dicey predicaments as of late.
Like when I''m pulling ice giants in everchill, and halfway through a kill another pops through the wall ontop of my group. Or when we're medding after an IG, and we have zero agro, and suddenly MOTEC busts through the wall like some bastardized frozen Kool-Aid man.
Scenario C has also happened in Catacombs when splitting sanctuary guards, so it's by no means zone or mob exclusive.
The easiest solution would be to, you know, just not be lazy and stop tagging mobs with a DoT. I thought however, that It wouldn't hurt to make this post and inform the staff and playerbase of a possible bug or at the very least, get a clarification from someone "in the know" about how Feign Death and Dot mechanics are supposed to behave. As of now it seems entirely too random to be working as intended.
Thanks,
Sean~
When using them to gain general agro on a random target in a hypothetical camp of three mobs, one of three scenarios will unfold.
a) I cast sicken on mobA. All three come. I flop, warrior tags mobB. I stand after mobA and mobC reset. Sicken is still ticking on mobA. I engage and kill mobB while sicken runs it's course. Mobs A and C never re-agro.
b) I cast sicken on mobA. All three come. I flop, warrior tags mobB. I stand after mobA and mobC reset. Sicken is still ticking on mobA. As soon as I stand mobA re-agro's and starts charging at me, bringing mobC with it.
c) I cast sicken on mobA. All three come. I flop, warrior tags mobB. I stand after mobA and mobC reset. Sicken is still ticking on mobA. I engage mobB. Sicken runs its course on mobA. Now, at any random moment mobA has the possibility to re-agro me. It could be when mobB is still at 50%, or it could be 3 minutes after mobB has already been slain. The DoT on mobA will have run it's course long ago, but for whatever reason I still remain on it's hate list.
---
Obviously scenario A isnt a probblem, and scenario B? well, I assume thats how game mechanics are supposed to work to begin with. Scenario C on the otherhand has caused some pretty dicey predicaments as of late.
Like when I''m pulling ice giants in everchill, and halfway through a kill another pops through the wall ontop of my group. Or when we're medding after an IG, and we have zero agro, and suddenly MOTEC busts through the wall like some bastardized frozen Kool-Aid man.
Scenario C has also happened in Catacombs when splitting sanctuary guards, so it's by no means zone or mob exclusive.
The easiest solution would be to, you know, just not be lazy and stop tagging mobs with a DoT. I thought however, that It wouldn't hurt to make this post and inform the staff and playerbase of a possible bug or at the very least, get a clarification from someone "in the know" about how Feign Death and Dot mechanics are supposed to behave. As of now it seems entirely too random to be working as intended.
Thanks,
Sean~