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

Lone Reaver could have terramex targeting #5405

Open
sprunk opened this issue Dec 21, 2024 · 1 comment
Open

Lone Reaver could have terramex targeting #5405

sprunk opened this issue Dec 21, 2024 · 1 comment
Labels
feature replay Contains a replay that needs to be watched. UX

Comments

@sprunk
Copy link
Member

sprunk commented Dec 21, 2024

I got a report/request that Reaver should fire at terramex (with a replay where it would have come in handy https://zero-k.info/Battles/Detail/2062177 ).

According to #4513 Reavers no longer shoot at terramex because they teamkilled each other too much, but (esp. in a 1v1) you often have a lone reaver. Would be nice if it could still fire in "safe" situations. Truly lone Reavers are easy to detect (Spring.GetUnitNearestAlly in radius, ok if nil) so perhaps that's already an improvement that doesn't introduce too much complexity.

@sprunk sprunk added feature UX replay Contains a replay that needs to be watched. labels Dec 21, 2024
@GoogleFrog
Copy link
Contributor

GoogleFrog commented Dec 21, 2024

I'm a bit wary of giving units too much situational awareness, as it makes their behaviours harder to learn. Maybe the solution would be a shoot-at-terramex toggle that can be disabled by default for Reaver, and the behaviour could even be added for a few other even more borderline units. Toggles aren't great in general, but this is a pretty hardcore problem so perhaps they're ok in this case. I wouldn't even show people the toggle on the UI by default. The behaviour might currently be tied to the wardfire toggle, which is a bit of an ugly combination, so adding a distinct toggle would be an improvement regardless.

Tbh I might even disable this toggle by default personally, since I haven't gotten much out of the behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature replay Contains a replay that needs to be watched. UX
Projects
None yet
Development

No branches or pull requests

2 participants