-
-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wreck decay problems #480
Comments
I suspect that a sinking craft can not bypass the minHeightLimit set in the type file. |
There seem to be two things with this issue. The first is whether or not sinking crafts should obey their min height limit. In previous versions I'm not sure the behavior here, since AP always ran our craft types with a min/max limit of the world limits (for the most part). I've created a separate issue to track this: #521. The second is a problem in the handling of sinking crafts, and this part affects much more than just torpedoes, and likely won't get fixed until we can get around to rewriting wreck behavior (after much internal rewriting). I've updated the issue title to reflect this new direction for the issue. |
Does this still affect the latest versions? |
Describe the bug
A torpedo set with a MinHeightLimit that isn't low enough that that torpedo sinks and hits the ground or ocean floor when it runs out of range is immortal and does not release.
Basically, what happens is that the torpedo flies normally and then sinks when it reaches its max range. But it sinks down and stops at the MinHeightLimit set. But if it does not hit a block as it sinks, it sits floating in the air piloted and does not release itself unless replaced with air using world edit.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The torpedo should probably be able to sink below its MinHeightLimit and/or should automatically release itself once it reaches the min height limit when sinking.
Screenshots
Versions (please complete the following information):
Additional context
Craft File:
The text was updated successfully, but these errors were encountered: