Misleading number of savestate slots shown
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
The folder where savestates are stored shows only the 100 latest savestates, the default value of 'max auto-increment savestates to keep', but the save slots selection menu shows 999 as the largest slot.
Expected behavior
The highest slot number should correspond to the number selected for the 'max auto-increment savestates to keep' setting.
Actual behavior
App shows slots up to 999, but deletes older savestates when the setting's limit is exceeded via auto incremental saving.
Steps to reproduce the bug
- Select any number for the max limit setting.
- Open the Save slot selection menu and scroll to the bottom.
Version/Commit
You can find this information under Information/System Information
- RetroArch: 1.19.1
Environment information
- OS: Android
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
No source files or tests are named. Reproduce the issue on the save slot selection menu after changing the max auto-increment savestates setting, then trace the menu and setting handling. Done means the highest displayed slot matches the configured limit while older savestates are still removed as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100