You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #3417 it's mentioned that the amount of crash dumps can take up quite some disk space. Now that #15101 is merged and crash dumps are nicely contained in a separate folder, this should be more straight-forward to implement.
Some options:
Automatically remove all crash dumps on game boot
Automatically remove crash dumps older than a set amount of time
Automatically remove crash dumps when folder exceeds a set size limit or number of dumps limit (like autosaves)
Warn user when the total space exceeds a set size limit or number of crash dumps
Provide a way to let the game clear them
Just like with the 'autosave' folder, players aren't supposed to use the 'crash' folder to store their parks. There are situations where a player wishes to restore (parts of) their park though, and require the save file for this even if it's corrupt. I think the least amount of work while still considering a player's lost work would be to only remove old dumps without warning.
The text was updated successfully, but these errors were encountered:
In #3417 it's mentioned that the amount of crash dumps can take up quite some disk space. Now that #15101 is merged and crash dumps are nicely contained in a separate folder, this should be more straight-forward to implement.
Some options:
Just like with the 'autosave' folder, players aren't supposed to use the 'crash' folder to store their parks. There are situations where a player wishes to restore (parts of) their park though, and require the save file for this even if it's corrupt. I think the least amount of work while still considering a player's lost work would be to only remove old dumps without warning.
The text was updated successfully, but these errors were encountered: