-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fix: Keep disabled Helix attachment upgrade buttons in Command Set #1542
Conversation
b9fe090
to
b3de98d
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.
Good change. Any reason to keep the legacy command sets?
I kept the legacy command sets in case some mod map uses them. |
Surely this patch already contains or will end up containing changes that result in similar incompatibilities? Are we limited to changes that won't affect some abandoned mod map from a decade ago? Cleaner / more manageable ini files feels more beneficial to me. |
Even if we have some changes that make mod map already incompatible, we can still curb removals, because then there are less things mod maps need to change to adapt to patch. |
What legacy command sets? I thought we agreed to revert the bomb buttons |
Helix Command Set count was reduced from 4 to 1. |
Count of What? I don't see any difference, can you explain? |
This change simplifies Helix attachment Command Set. Buttons will no longer disappear after research. This means shortcut key can be used on multi Helix selection to build an upgrade any time.
This behavior is consistent with USA vehicle drone upgrade buttons.