-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Consider AutoTarget ScanRadius when attack moving #20257
Conversation
I wouldn't call it a revert, you made it configurable which looks like the right way to go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I misunderstood the change and thought this would solve the problem by moving it to a per-unit setting in .yaml
Doubts were voiced in https://discord.com/channels/153649279762694144/388282819371204608/1018848213408690237 that current behavior is intentional.
The first part is crucial for melee units, as they fully rely on ScanRadius. The second part is there to keep the behaviour consistent and not introduce any code landmines for the future from the behaviour mismatch |
Testcase in RA - spies. They have a long autoscan radius |
@abcdefg30 I seem to remember you were not convinced by something here? |
I wasn't convinced about the attack-move behaviour, but I think this PR is fine for now. (The problem is units endlessly chasing instead of moving to their attack-move target. But that is OK in this PR since it only applies to units in the AttackAnything stance.) Hence I removed the label. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK. Hopefully this will get thoroughly tested during playtesting.
closes #17503
After 4 years melee units will be able to attack move again
This PR basically reverts #16942 for units on AttackAnything stance