Monster AOEs and Target Switching

[coldreactive]

When a monster first spawns, and its first attack is an AOE... you will attack them, but they still run to whoever they initiated the AOE attack to instead of whoever they switched targets to. Please change this so that Monsters / enemies will instead cancel their aoe and immediately re-use their AOE on their new target instead.

[Souljacker]

There's quite a bit about this whole "attack queuing system" that needs to be reworked. A monster shouldn't continue its path across the room to smack a mage after a provoke.

[coldreactive]

There's quite a bit about this whole "attack queuing system" that needs to be reworked. A monster shouldn't continue its path across the room to smack a mage after a provoke.

Indeed. As a note, "Provoke" the move however does not work if you have aggro of the monster you're using "Provoke" on, which should be added to its tooltip.

[NyneAlexander]

There's quite a bit about this whole "attack queuing system" that needs to be reworked. A monster shouldn't continue its path across the room to smack a mage after a provoke.

This brings up, what I feel, is a crappy mechanic with provoke. Instead of moving the user to the top of the hate list, it should reduce the hate of everyone else by a margin.

[Lemuria]

When a monster first spawns, and its first attack is an AOE... you will attack them, but they still run to whoever they initiated the AOE attack to instead of whoever they switched targets to. Please change this so that Monsters / enemies will instead cancel their aoe and immediately re-use their AOE on their new target instead.

This should really occur on targets that haven't actually USED their AoE yet, but are moving into position to do so, otherwise it could be abused by tank swapping.

I know what you meant, but it needed a little rewording. Personally, I find it both hilarious and silly that a mob will continue its bloodlust for its chosen target regardless of whom it hates the most.