If this seems written awkwardly, whenever I write a bug fix or workaround I try to use as many keywords as possible so anyone searching for my solution can find it easily later. I have renamed my old one to ghost cyclops and sunk it to the bottom in a trench with all the lights off. For now, I cannot get a Seamoth explosion or disappearance to occur in my new Cyclops. Still testing though, will determine later if this fully fixes it. Meanwhile, completely stripped of all construction, and all items removed, the old cyclops still blows up a seamoth. So far testing indicates the new cyclops will NOT cause a seamoth issue or bug, both virgin, and with all my old construction such as storage lockers and plant pots moved. Have not tested with a second constructed cyclops, only a console spawned one. With luck the new cyclops should be free of the glitch. Then hit f3 again, escape again, and ~ key. If you have an explode or disappearing seamoth in cyclops hit f3, escape, and click the disable console commands button in the upper left corner. Apparently the cyclops construction itself can bug out and make a cyclops that explodes a seamoth.

Apparently the issue is in the construction of the Cyclops itself. The issue is NOT with the Seamoth like many assume. Here is my post talking about it on the steam bug forums:Īfter testing, a workaround / bug fix to seamoth exploding / disappears when in the cyclops bug in subnautica has been discovered by me. After testing today, it turns out the issue is the cyclops itself. The issue with creating a new Seamoth or a new console spawned one is that mine would just explode again.

Subnautica repairing cyclops