[Feature Request] Add exit options that prompt the user to save state or discard progress
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
What feature are you suggesting?
Description
Currently, when closing a game or exiting the emulator, there’s no prompt offering to save the current state. This can occasionally lead to data loss if the user forgets to manually save before quitting.
In order to prevent data loss if the user forgets to manually save before quitting I suggest adding options to the exit prompt.
RetroArch
Current Quick Menu labels
Close Content
Save States
Save States → Save State
Feature request
Proposed added Quick Menu label: Save State and Close Content
Close Content
Save State and Close Content
Save States
Save States → Save State
Enable/disable Show "Save State and Close Content" menu label
I recommend that the proposed feature "Save State and Close Content" be disabled by default.
To enable it, a new menu entry could be introduced:
Settings → Saving → Save States
With the following options:
- Auto Save State (consolidated from Settings → Saving → Auto Save State)
- Show "Save State and Close Content" menu label
Another emulator with this feature: PCSX2
Menu bar
- Shut Down -- Prompts "Are you sure you want to shut down the virtual machine?" Yes (button) No (button) "Save state for Resume" (checkbox)
- Shut Down Without Saving
- Exit -- Displays the same confirmation prompt as Shut Down
10-foot user interface
- Close Game
- Exit and Save State
- Exit Without Saving
Why would this feature be useful?
- Prevents accidental loss of progress.
- Improves user experience and reliability.
- Aligns behavior with other emulators that already include this safeguard feature.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing Quick Menu "Close Content" and "Save States" flows, then review Settings → Saving → Save States and the current Auto Save State setting. Define the enabled and disabled menu behavior, confirmation or save-state flow, and migration of the setting before implementation; done means the new option works without changing the default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100