Changes between Initial Version and Version 1 of Ticket #13432, comment 5
- Timestamp:
- 05/20/22 10:49:23 (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #13432, comment 5
initial v1 1 1 Thanks for your response. I understand your concerns are about non-existent saved games (dummy savenames) being listed in this dialog, because in its current form, the dialog doesn't relate to this situation. However, I'm curious as to what you consider is your ideal outcome. 2 2 3 Is it a change in the dialog's messaging ?3 Is it a change in the dialog's messaging (which would also apply to the in-game dialog)? 4 4 Should these entries be generally excluded from the dialog, even though their presence indicates a problem with the savename (under current testing criteria)? 5 5 Perhaps the name-testing criteria should be adjusted to exclude savenames which don't have an existing saved game (ie. dummy savenames)? 6 Should we remove this dialog and just rely on the in-game warning message? 6 7 7 8 If you believe that non-compliant dummy autosaves are likely to be a significant issue across multiple games (and thus appear in this dialog), then changing the current testing criteria to exclude dummy savenames is probably the way to go. … … 9 10 10 11 By the way, did you try starting a new game of Future Wars, then wait for an autosave to confirm if it triggers the in-game warning? 11 I expect it would, but if not, then the solution to your issue may reside in the testing code within saveAutosaveIfEnabled(). 12 If it doesn't, then the solution to your issue may reside in the testing code within saveAutosaveIfEnabled(). 13 14 From the user's perspective (if no changes are made), the in-game dialog remains the best solution for resolving dummy autosave issues (assuming it's triggered, and even better if it's not), by allowing the user to overwrite the dummy savename with the autosave (thus creating the autosave saved game)... something the Options dialog can never do!
