Big0Toe

Hi, just yesterday I installed the carrier command mod on my server and happened to run into crashes too. The mod was installed around 17.30 CET and the first crash occoured around 2h later, a connection lost error showed up and nobody was able to enter the sever until I restarted it. Active Players at that time were 2. After the restart it ran fine for another two hours until it crashed again. Player Count at that time 3. We had to restart the server again and after relog the server wasn't even up for 10 minutes before it crashed again. Active Mods are regenerative astroid fields and carrier commands. Those are the logs before the last crash. Strange thing is, that at least one of the ships mentioned here "Goin I" is a mining ship, controlled by the AI. It's set to "Mine" and had no interaction with the carrier command script. I might be wrong here, but it seems weird to me, that exactly this ships name shows up with a "Wreckage found" and "fighters started" note. It has a hangar with mining fighters tho. The logs of the 2ndCrash look rather similar in the end, before it went downhill. Last entries in Logs for 1st Crash I really love this mod (even tho I could only use it for 4h :D ) but in this state I have to deactivate it, so we can keep playing on our server. However I would love to help narrowing this issue down, so if I can do anything, let me now. This happened for me too :) Script Version 0.10.1 Avorion server Beta 0.16.7 r11165 4b472bf34ee5 running on Ubuntu 16.04.4 LTS starting up in "galaxies/MyGalaxy" CPU: Intel® Core i7-4790K CPU @ 4.00GHz 8 Cores RAM: 31GB (3GB reserved for our server) Nitrado - Server port: 27000