View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003044 | Dwarf Fortress | Technical -- Saving/Loading | public | 2010-08-16 16:19 | 2010-08-22 14:40 |
| Reporter | Silverionmox | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | no change required | ||
| Platform | pc | OS | win | OS Version | 7-64 |
| Product Version | 0.31.12 | ||||
| Summary | 0003044: Autosaving saves twice | ||||
| Description | When autosaving, the autosave is created normally. So far so good, but the save that was used to load is /also/ overwritten. That's unnecessary. | ||||
| Additional Information | As long as the responsiveness of the dwarves is lacking due to bugs, that's annoying when trying to recuperate a fortress after an AI quirk, only to discover the disaster has been overwritten on the good save. In addition, when loading an autosave it saves back on the autosave - with the original date - even when you've advanced a season or three. And that's ridiculously confusing. | ||||
| Tags | No tags attached. | ||||
|
|
So far so good, but the save that was used to load is /also/ overwritten. That's unnecessary. How's that different from how saving normally works in DF? Also, have you tried enabling autobackup? In addition, when loading an autosave it saves back on the autosave - with the original date - even when you've advanced a season or three. And that's ridiculously confusing. See this suggestion: http://www.bay12forums.com/smf/index.php?topic=57735.0 |
|
|
It's the autobackup I'm talking about. (seasonal save) It saves on the loaded game, and creates a new, identical, save. It should save on either, but not on both. Even when using autobackup the player will still exit normally if nothing goes wrong, and then is the time to overwrite the loaded game. Doing it twice accomplishes nothing and uses system resources. That's a bug. The obtuse save names on the other hand are probably indeed as dysfunctional as allowed. Although then I don't comprehend the bother to include the names, if displaying 1. the date and time of the last file change and 2. the date in the df world would accomplish the same,without needing to write the code to put it in a soon-to-be-obsolete string. |
|
|
Doing it twice accomplishes nothing and uses system resources. That's basically the definition of a backup. This aspect of the save system is clearly working as intended, and the alternatives hardly seem less confusing. Feel free to make a suggestion about it, though: http://www.bay12games.com/forum/index.php?board=5.0 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-08-16 16:19 | Silverionmox | New Issue | |
| 2010-08-16 18:49 |
|
Note Added: 0011838 | |
| 2010-08-16 18:49 |
|
Tag Attached: AWAITING UPDATE | |
| 2010-08-22 14:22 | Silverionmox | Note Added: 0012021 | |
| 2010-08-22 14:33 |
|
Tag Detached: AWAITING UPDATE | |
| 2010-08-22 14:40 |
|
Note Added: 0012022 | |
| 2010-08-22 14:40 |
|
Status | new => resolved |
| 2010-08-22 14:40 |
|
Resolution | open => no change required |
| 2010-08-22 14:40 |
|
Assigned To | => user6 |
