Preesh wrote: ↑Fri 14 Aug 2020 6:30 PMwrote: It most certainly existed 3 weeks ago already, it existed at least since before the archer changes were made as I noticed this behavior while testing as well, as it is a client only thing it's most likely that it existed at least since the 1.125 client, likely even before that.
Here's a video of this "existing" a few weeks ago. Just listen to the taps and watch the combat log.
That is indeed strange then. Like I said, I know the behavior exists at least since before the archer changes as while testing those I noticed it. It would be really interesting to see if anyone isn't affected by this at this moment. Anyways, in that case we can rule out an inherent 1.125 issue and something else must trigger this client behavior. Would be especially interesting if a linux person is affected by this or not.