Collision explosion fix #692
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
add trackedlocations
reimplement TrackedLocation to specification
use built-in methods for vector manipulation
Resolve merge
Fix merge and build
TylerS1066
approved these changes
Aug 15, 2024
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.
This removes the abilities for crafts with
CollisionExplosionto no longer explode inside its parent craft. This feature can be re-enabled throughallowInternalCollisionExplosion: truein the parent craft's craft file.Checklist
Note: I am not sure why but the 17 commits seem to do nothing. If this is not benign, please let me know how I can address this. I think something went wrong when I was working on tracked locations.