Suggestion about new feature on currently savestate...
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
I don't know if i can do here....... if not sorry me and i can register on forum if need :)
Description
I have already made this feature on retropie official forum....
they invited me to contact you to see if it could be interesting.
Sorry for me but my english it's not very good......... i thinks i can report here the thread i made on retropie forum:
https://retropie.org.uk/forum/topic/30599/retropie-retroarch-possible-savestate-addictional-feature-check-if-savestate-exist
Expected behavior
I suggest to add a feature to understand if, when you load a roms whit a specific core, for this core it's already present the savestate files.
Currently it's possibly to select the used slot...... default it's 0. But if you run a games and you already use in the pass the savestate you don't know it. I have suggest a way to made the number slot whit a different color... for example RED if the slot it's used or GREEN if not......
Version/Commit
You can find this information under Information/System Information
- RetroArch: mmmmm.. on retropie currently commit... 4.7.12 (if i remember correctly) for a raspberry pi4. If i remember the retroarch it's 1.8.8
Environment information
- OS: Retropie
- Compiler: I don't know........
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 reviewing the linked RetroPie forum discussion and tracing how RetroArch selects savestate slots and presents them in its frontend. Define how existing savestate files should be detected for a ROM and core, how occupied and empty slots should appear, and how this should work across supported environments.
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
- Needs clarification
- Newbie friendliness
- 25/100