Whenever you pause melee combat to cast a spell, then attempt to resume melee combat the game code fails consistently (6 times out of ten) to resume melee, even when you make multiple mouse clicks on the intended target ; this usually involves a hero surrounded by a lot of trash mobs ; it appears that all cpu cycles are consumed by the tens and sometimes dozens of "swings" being asserted by the large numbers of trash mobs. In the meantime you just stand there like a dope doing nothing except bleeding to death.

This happens with such consistency that it cannot be a code misread - its just a bad melee mitigation algorithm. The failure to re-assert player melee (via mouse input) is very hard to accept. I for one , do not feel that standing doing nothing while being beaten to death is an entertaining form of a contest, while I click like crazy with the mouse on the target I wish to resume hitting.

Can you please provide some specific examples?

I have noticed that attacks are queued, however, based on holding the mouse key down, which means that I have to wait for the queued actions to complete before I can take another one. For example,

Shooting bolts by holding the mousekey down. After letting go of the mousekey, I have to wait for several more bolts to fire before I can launch another skill. Similarly, when fighting (especially with 1h ludi weapons), I have to wait for the queued attacks to complete before I can successfully launch a skill.

Is this what you're referring to?

This is currently on our Known Issues list (for both v0.91 and 0.95 (PTS)). Thanks for the report though, it is a pesky bug indeed!

Quote:

---

Auto Attack will be interrupted after using skills from hotkeys 1-5. You can re-click the mob to continue auto-attack.

---

Known Issues 0.91

Ah yeah - that bug - glad to see it's being fixed:)

thank you for an aknowledgment of the issue. The difficulty I experience is that after interruption - re clicking the mouse FAILS to resume melee about 6 times out of ten. This can be partially mitigated (unreliably) by double clicking the left mouse button on your intended melee target, to initiate/resume melee combat.

I believe some part of the queing code is associated with the problem due to the fact that :
(1) this most often happens when there are more than 8-10 trash mobs supporting the boss - and they are all queing up their swings at me ; their misses/hits scroll up the screen while i stand there helpless ;

(2) It appears to occur less frequently and/or with shorter duration - if I ignore the boss i want to kill and focus on thinning out the large number of trash mobs.

I presume/guess this helps because there are no longer 2 dozen "objects" queing up their melee swings , and it appears that once the mob size gets back down to 2-3 bosses with 8 or less trash mobs, my melee attack is able to re-assert itself.

This statement therefore is partially correct: "Auto Attack will be interrupted after using skills from hotkeys 1-5."

And partially incorrect: " You can re-click the mob to continue auto-attack."

Reclicking currently functions unreliably.

I very rarely have an issue reacquiring my target after using a hotkey spell. I have seen what you are talking about but not with the frequency that you are seeing.

There are no issues regarding target aquisition or re-aquisition; the issue is re-initiating melee "swings/attempts" after using a hotkey spell.

My guess is that because actions can be "stacked" or "que-ed", once a player object stops swinging their priority in the melee que is erased and all que stack space is consumed by a.i. mobs/objects - causing a player to stand and do nothing after attempting to re-assert melee initiation.

The assertion may register, but since there is no free space in the que stack (due to mob count/que-overflow), there is no sequencing available to a player object once the que has been filled by a.i. mobs.

I've been trying to test the theory this phenomenon is due to que overflow due to mob size; one interesting observation is that immediately after casting righteous stomp (no one in the mob can take any action except get up and run back to attack player) - I have no trouble at all resuming melee, or successfully executing an rmb (right mouse button) attack.

So i remain of the opinion that the inability of a player to re-assert attack sequencing (after hot key use) is due to all action priority being consumed by the a.i. <end note>