Fix Czar missing carrier auto deploy functionality #6549
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.
Issue
CZAR does not have the
CARRIER
category, soblueprints-units.lua
external factory processing for carriers does not pick it up:fa/lua/system/blueprints-units.lua
Lines 675 to 698 in 3f034d1
Description of the proposed changes
blueprints-units.lua
.StatToggles
blueprint field. Not sure why it was incorrectly written in Adds stat toggle infrastructure and switches AutoDeploy to use it #5581 5dcaac5Testing done on the proposed changes
The button's description is corrected, and when you right click it gets highlighted and constructed units automatically deploy.
Additional context
This is the second bug I've seen because of CZAR being a flying carrier, the first being that intel/counterintel remains enabled for units inside the CZAR because its base class is that of an air transport and not a (naval) aircraft carrier.
Checklist