[Feature Request] Multiple Battery Save Blocks (RETRO_MEMORY_SAVE_RAM)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Some games/cores have more than one battery-backed save memory region, and they are not always contiguous.
It would be useful if the save interface supported multiple battery save blocks, stored separately on disk (for example: *.srm, *.srm1, …).
This would allow proper handling of all save regions without merging or losing data.
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 RETRO_MEMORY_SAVE_RAM save interface and the code that writes battery-backed memory to disk. Determine how multiple non-contiguous save regions should be represented and named, then verify that each block is stored separately without merging or data loss. The issue names no files or tests, so the relevant entry points still need to be located.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100