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

Guard/AttackMove order inconsistencies with non-autotargeting units #18005

Open
abcdefg30 opened this issue Apr 29, 2020 · 1 comment
Open

Guard/AttackMove order inconsistencies with non-autotargeting units #18005

abcdefg30 opened this issue Apr 29, 2020 · 1 comment
Labels

Comments

@abcdefg30
Copy link
Member

Units that only have Guard or AttackMove but not AutoTarget cannot activate their OrderGenerator when solely selected. They can only enter a Guard or AttackMove activity when ordered in a selection together with at least one unit that has both Guard/AttackMove and AutoTarget.
Example: Engineer in RA cannot guard when selected single, but can guard when selected together with a rifle man.
One way to handle this would be giving meaning to Guard/AttackMove for non-autotargeting units (#18004, and AttackMove turning completely into a regular move). Another option would be to completely skip those units when ordering a guard or attack move. (Like buildings are skipped when you order a move command.)

@KOYK
Copy link
Contributor

KOYK commented May 2, 2020

Maybe skip the guard command by default when in groups and only use it with the combination of ALT key? And when the unit is selected alone then use it any way, without ALT key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants