"....Killed" server closing after using Rmove signs and a non cruise on pilot torpedo

[MysteryTimeTrav]

Describe the bug The server appears to close with only the message "....Killed" after using a torpedo configured to use static move signs and collision explosions a couple times. No error messages given in both server logs or console but a ton of Null pilot craft releases.

Server Logs: https://pastebin.com/66Bwuse9 Console: https://pastebin.com/x1RCyc1Z

To Reproduce Steps to reproduce the behavior:

1. Pilot a Torpedo like craft file that has static move enabled, collision explosions, and does not cruise on pilot.
2. Set the craft cruising using a cruise sign and move around using the Rmove signs
3. Hit something with the torpedo like craft
4. See large amount of Null pilot released crafts
5. Possible server "crash" or close with "....Killed" message

Expected behavior Craft just releases after sinking without closing server or at least gives an error message to the problem.

Screenshots No screenshots available.

Versions (please complete the following information):

• Movecraft: 8.0.0-a.2
• Java 11 - OpenJ9
• Minecraft e.g. 1.16.5

Additional context The torpedo doesn't seem to sink completely to the floor when it hits. The remains of the torpedo after the hit fall for about 10 blocks and then stop.

[TylerS1066]

This issue also ties into #438 and will require a large number of changes to fix.

[TylerS1066]

After fixing #438, I'm not so sure these two are the same.

I'll have to take some time to try and reproduce it later, but if you want to please try the upcoming alpha release with this problem.

[TylerS1066]

Just checking in, does this still happen with the latest dev build?

[goodroach]

Something similar happens, but now movecraft just stops when you fire a torpedo while you are cruising. This happens more often when you fire multiple torpedoes.