Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shift queue attack move order bug #16924

Open
Punsho opened this issue Aug 10, 2019 · 3 comments

Comments

@Punsho
Copy link
Contributor

commented Aug 10, 2019

To see the issue hold shift then press and release a then hold a. First mouse click will be an attack order followed by a MOVE order then followed by attack move orders. That move order shouldn't exist

@matjaeck

This comment has been minimized.

Copy link
Contributor

commented Aug 10, 2019

Can you provide a reproduction? I'm not sure if I can reproduce the issue.

@Punsho

This comment has been minimized.

Copy link
Contributor Author

commented Aug 10, 2019

I can reproduce it on bleed and on the second devtest with the provided steps

Attackmove
attackmove2

@pchote

This comment has been minimized.

Copy link
Member

commented Aug 10, 2019

The A key isn't a modifier, so it will behave the same way as holding down any other key in your OS. This will typically do nothing for a couple of hundred milliseconds, then spam the key event at an OS-defined repeat rate. If you click before the repeat kicks in, or between the repeat cycles, it will (correctly) issue a move order. This is visible in the animation by the green move cursor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.