Remove OLDLST campaign overrides. #19153
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Smittytron
approved these changes
Feb 13, 2021
|
I think TD is also missing shore directions for the new LST to make sense. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We originally added the lstnew sprites and configured the default
LSTactor to use them in the hopes that they would be useful for custom maps and maybe even as a buildable unit. In practice, this never worked out, and the missions all switched to the original artwork to avoid issues.These overrides are a problem for the remastered assets projects, as SDK-based mods aren't able to override map sequences. Considering that we don't use the custom sprites, and that they aren't compatible with the remastered assets, our best approach is to switch the base
LSTactor definition to the standard campaign actor and drop all the workarounds.