Worrisome Wamouras.

[Byrthnoth]

They'll deagro with DoT on, and if it's time based then it's time since agro and not time since last action.

On Ice/Thundersday I used to do something like:
Pull a Prince with T4, Grav, Run back, B4, T4, Bio II, Drain, Bind -> /heal to get a tick or two before it dies for Chain 3.
And I had them despawn on me like that, remarkably quickly too. They'd deagro while still gravitied, bound, and DoTed.

It's like they just hit certain windows since the first action/their last hit/something I don't know and decide to deagro.

[Thorny]

30 seconds out of tracking range = deaggro, old

if you stay >10' on wamoura you're going to be out of tracking range constantly and get a lot of deaggros(sound so 10' in any direction)

puddings are sight and pretty short range, i believe also 10'

[Amok]

They'd deagro while still gravitied, bound, and DoTed.

That's pretty unique I'd have to say. From the testing I've done I've never gotten any mob to deaggro while bound or slept (other than worms).

[Byrthnoth]

That's pretty unique I'd have to say. From the testing I've done I've never gotten any mob to deaggro while bound or slept (other than worms).

Well, trust me it can happen. And don't think I enjoyed losing chain when I had a DoTed monster at 1%. I've never had it happen on anything but Princes though, so it might have something to do with their changing forms animation?

[Doink]

It's actually a predictable bug that can be used to your advantage, when one bug tries to deaggro I've found that almost all will do the same. I just get myself into a rhythm nuke, grav, run a little less than normal, start casting nuke, mob goes yellow "sort of binds itself", nuke lands a couple seconds later.

Hell if SE isn't gonna fix this garbage, might as well take advantage.