Fix a bug and extend the context based templates feature #6015
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the proposed changes
Related to this bug report on Discord. The bug was that a tech 1 engineer can not create the storage template when trying to cap a tech 2 extractor because the tech 2 extractor would block the template as a tech 1 engineer can't build it. We fix that by trying to build the unit it upgrades from, or by trying to build the unit it originates from.
Next to that we extend the feature by allowing it to act like a color picker - if we're hovering over a unit or a build order and we can't find matching templates then we'll try to enter command mode with a build order for the given unit and/or blueprint order. This is inspired by the featured of @4z0t mentioned on the forums.
context-based-templates-100.mp4
Testing done on the proposed changes
Spawning in structures and triggering the hotkey in various conditions.
Checklist