Fix Megalith's GetCommandQueue not functioning as expected #6578
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
When checking the Megalith's
UserUnit:GetCommandQueue
, it would return its default factory rally point instead of its own move orders.Description of the proposed changes
FACTORY
category that causes this behavior.CONSTRUCTION
category as units that can start builds of other units but it would be incompatible with mods.Testing done on the proposed changes
Used the following command to confirm that units with the `FACTORY` category have this behavior.
Made sure that hotbuild issues the correct order so that Megalith can build a blueprint on the ground instead of building like a factory.
Additional Context
I noticed the Fatboy has the
CONSTRUCTION
category, but aircraft carriers do not, so Fatboy is a bit out of place for mobile factories.Checklist