Im not sure how this even made it past the PTR to be honest. I am also surprised the forums are not blowing up with complaints.
They are blowing up with comments, there are over 20 threads with the same thing, someone compiled them all into a megathread.
Edit: I believe I found the root cause of this issue, and the community managers have responded that they forwarded what I found to the dev team!! Good news everyone
Ah I was not aware of that, good that people are complaining. Granted alot of the complaints on these forums are useless and not constructive but this one is a BIG DEAL and needs to be Dealt with ASAP…
My guess on this is that they probably modified the player event queuing as a method to try to avoid the movement bugs that have persisted for months.
Those “movement” bugs were actually event queue bugs, that caused your character to miss the event that marked the expiration of a buff/debuff.
You’d get rooted (-100% movement buff) and if enough stuff happened or lag occurred the event that would be the removal of that buff would be lost and you’d be stuck wearing that buff/debuff until your character was completely despawned from the world (logging out for 2 min was the only solution)
In this case, it appears we are getting the actual inputs added to a queue instead of the events they are supposed to be triggering. You’re getting a bunch of “button press Q” in a stack of events, instead of “Ice Gauntlet Skill thats bound to Q”
One of those is much faster since it takes less conditional statements and lookups to see what Q was supposed to do at that moment in time. It’s a more timely system of storing the queue, but it lacks the context required to avoid this bug. Currently if you switch weapons quickly, its thinking you’re hitting Q “now” and then checking what weapon you hit it on.
It needs to store your weapon state (which one you have equipped at the time of button press) with the button press in the event queue, or this will continue to happen.
can’t do combos properly with this skill queue, it’s awful
bump make this option in settings bros
Ice block and void blade are some of the worst offenders and normally failing to properly switch/cast leads to a death so its a pretty big deal.
Its like they want to discourage button spamming but at the same time make it so you have to spam
certain abilities or they wont go off period.
Yea I agree, weapon swap should cancel any skill queue
Good-ish news, I believe i found the culprit and the dev team has been informed. When you press an ability, its activating both the top and bottom abilities. It can only be observed (because the weapon you hold locks what abilities are performed) when both cooldowns are counting down and the button is pressed, you see both the top and bottom ability turn RED indicating it was registering both as being pressed. Hitting the ability once after the cooldown starts queues the top ability and if the next button pressed is swap, it will activate that ability
Its almost as if nobody at AGS ever took a programming logic course
At begining, I had mixed feelings, but when get used to it and stop spam everything like before when all was unresponsive, already have no issues. Except like when I using consumables, Isometimes getting little pissed and asking to the ether how many fk times I have to press that to put it in that mouth…
it’s not about button smashing,
even if you just land an ice storm (in mine its, F, F), then immediately swap weapons, my character will perform whatever skill that I put in the F button.
Can we all just be careful when asking for this to be made into a Settings option as this can easily paint the picture of it just being something we’re not fans of rather than a fundamentally broken part of the system that needs to be addressed.
The setting option could be added in conjunction to addressing this queuing problem, but it shouldn’t be “the alternative fix”.
It is not a fundamentally broken system.
If they would simply empty the queue after weapon swap (remove the things that were put in before the swap), it will work just fine.
Also people should stop playing this like Strcraft…it is not an APM game.
It’s not broken in a fundamental way, but they need to empty the queue… so is it broken in quite the fundamental way or not?
Eh no? That is a really easy fix and then it is fine.
Fundamentally broken would mean the concept is not working and it can not be fixed.
I’m not discussing the difficulty of fixing it, I’m talking about the core aspect of the system which is making it unbearable to use. If you’re not participating in any high-paced activities then I understand why it’s not a problem for you, for the rest of us it is.

Whatever mate ![]()