Implement "DropStrider" input on dropships #281
Merged
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.
Dropships and striders have inputs and animations for being dropped directly into combat, but the feature was never finished. This PR implements that functionality.
This reuses a lot of logic from Combine soldier drop-offs, so most of the basic setup for mappers is the same (an
info_targetlanding point,OnFinishedDropoffafter it's done, etc.)A few notes:
StriderTemplatefield.OnCrateShotDownBeforeDropoffoutput.deployanimation.Test map: dropship_strider_test.zip
Does this PR close any issues?
PR Checklist
developbranch OR targets another branch with a specific goal in mind