Debug + DATA files growing extremely large

[Kyoretsu]

I'm having an issue with my DATA file growing extremely large. I tried deleting some of the old files like I did for my DEBUGRAW folder, but that ended up deleting all of the ships in that world (I had a back up). What can I do about this?

 

[Zackey_TNT]

There isn't much you can do.

Deleting any folders inside the data file may result in world corruption.

Starmade gets quite large, But it shouldn't go over 15GB (What sized disk do you have? Throw a 1TB hard drive in there. Honestly they are like 60$)

All I can suggest is to join a server and let them deal with the problem or delete ships and save them via blueprints.

 

[Kyoretsu]

There isn't much you can do.

Deleting any folders inside the data file may result in world corruption.

Starmade gets quite large, But it shouldn't go over 15GB (What sized disk do you have? Throw a 1TB hard drive in there. Honestly they are like 60$)

All I can suggest is to join a server and let them deal with the problem or delete ships and save them via blueprints.

I am waiting on a SATA cable and a new version of Windows 7 to install my 1Tb hard drive. In the mean time I would like to continue building.

 

[Zackey_TNT]

I am waiting on a SATA cable and a new version of Windows 7 to install my 1Tb hard drive. In the mean time I would like to continue building.

The only way you can continue building while saving the current world is to zip the file move it to some other loc and start a new

Wait a min? The data file stores data for the game such as icons and programming stuff, Its not your save file server-database would be your save file

 

[AndyP]

You may want to disable:

DEBUG_SEGMENT_WRITING = false //Debugs correctness of writing of segments (costs server performance)

as this creates a catalogue of previous written segments, which would be used to restore chunks if a chunk is corrupted on load.
This is more an ancient function that was required for huge objects in mid/end 2014 where chunks randomly flipped blocks to other things or were missing forever. This function does not yield any benefits any more, its left in, IF they come back so we can turn this on again.
But the disk usage is really high with that on.

FORCE_DISK_WRITE_COMPLETION = false //forces writing operations of raw data to disk directly after operation. For some OS this prevents raw data corruption

This may be an option you want to enable, IF you have issues with reverting ship states, or problems with saving in single-player. (Sometimes new ships do not get saved at all, and revert to a marker without any block and then vanish shortly after, however this only affects a few combinations of systems, and the cause is most likely not Java)

- Andy