auto attack.

[Tsutsu]

It doesn't register half the time its pressed anymore when going into combat. It's really annoying to click it and nothing happen and not notice for a while........

[Glitchless]

What client version? What device? Hot bar? Mouse click? Keyboard hotkey? Are you under the effect of any substances?

[Tsutsu]

All versions, browser as well. via keyboard click. You used to be able to auto attack/range instantly after clicking "find enemy" that no longer works.

[Glitchless]

Ah, OK. That would have to be because both actions are on the secondary cooldown now. I can see how this would be rather annoying.

Looking into a fix now.

[Glitchless]

Doing a server reset and then a client patch to fix this issue. Movement will go back on a special version of the primary cooldown to prevent collision with turning on autoattack while entering combat.

[Tsutsu]

Originally Posted by Glitchless

Doing a server reset and then a client patch to fix this issue. Movement will go back on a special version of the primary cooldown to prevent collision with turning on autoattack while entering combat.

Awesome, you have saved the little bit of sanity I have left

[Huggles]

Now we can't enter combat right after exiting. =(

[Huggles]

This is worse. I did hundreds of fights in a row testing quad without any issues, but now it takes even longer to hit attack than what Tsu was saying because of the cooldown to enter combat.

[Glitchless]

The exact length of time between finishing combat and hitting autoattack is far less important than whether or not it works 100% of the time when you hit it immediately after entering combat.

[ShadeDaScout]

now we can't move right after fight ends :[

[Huggles]

Originally Posted by Glitchless

The exact length of time between finishing combat and hitting autoattack is far less important than whether or not it works 100% of the time when you hit it immediately after entering combat.

https://www.youtube.com/watch?v=gSi4Q2qFKgw

Looks like it was working pretty much 100% of the time. You can see the tiny little 0.1 second cooldowns when I click attack right after I click enter. Only issue I could see is if he's hitting attack so fast after entering that it's not even registering him as being in combat yet, in which case he could just wait literally 1/10th of a second in between hotkey presses.

Video proof > no proof, in my opinion

[Glitchless]

The problem was something we tested and were able to easily replicate. The fix and delay after exiting combat will remain as is.