Open Zhusiyuan354 opened 5 months ago
Ditto on this issue, except in my case the world generated with 100 ships of 0.0 mass (possible incompatibility with another mod I'm using)
Either way, when a ship has a mass of 0.0, the game appears to continuously panic into the server log before eventually crashing and generating gigabyte-sized crash logs. I am unfamiliar with VS or Eureka's source, but it seems that ships that are empty are not handled properly by the game.
log spamming also happens on fabric 1.20.1 with no apparent cause.
This issue occurs when only Valkyrien Skies and addons are installed and no other mods
Minecraft Version
1.18
Eureka version
ver 1.5.1 beta.1
Mod Loader
Forge
Issue description
This happened when I updated Eureka to the latest version and got a explosion near my physics-ship.The whole ship was thoroughly destroyed and then the command consle started report that: It had no possbility to stop it. I can't find the ship which has this problem by using vs ship through the ship's ID , until I tried vs delete @v. That deleted ALL MY SHIPS, Painfully.
Issue reproduction
Sometimes I realized that could be a radom event, not just explosion can reproduce this problems, so I described it as a bug.
Logs
You would not want to see that,because almost all the files are written with this error. latest.log