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
Move ValidRelations from Capturable to Captures #20261
Conversation
1c8d62e
to
1944e6a
Compare
I think if we want a real improvement (in flexibility) we should have both. Otherwise this is simply moving stuff around for no actual gain (well yes, consistency). |
we gain the ability to treat capturing as a weapon, if we keep on the capturee we'll lose that again |
Okay, how do you denote that "this is a special structure that can be captured by an/any friendly capturing unit (engineer)"? |
See TD engineer in this PR. For me this is a necessary step towards |
1944e6a
to
7470e32
Compare
7470e32
to
df22f1e
Compare
6daad0a
to
1179053
Compare
c481a99
to
690484a
Compare
34a737f
to
8f0fae9
Compare
8f0fae9
to
01417a7
Compare
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.
Motivations seem reasonable enough to me.
01417a7
to
4a79766
Compare
Fixed |
To better match weapon definitions
4a79766
to
6bea79b
Compare
When working on adding auto-target for
Captures
I noticed that valid player relationships is defined onCapturable
instead ofCaptures
. This is the complete opposite of how we define weapons, we put ValidRelations on warheads and projectiles. Not on the targets.