[Feature Request] "Save Runtime Log (Per Content Directory)"
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
You can already sort stuff like saves per content directory, but for some reason not runtime logs.
Using Retroarch on a low-end portable device, I find myself using multiple cores for a single system, so saving runtime logs per core isn't ideal, as sometimes I'll start a game on a core, just to switch to another one later, thus, breaking the playtime in two.
"Aggregate" also isn't a good solution, as it can get pretty messy when you're emulating various systems, also, games of different systems with same name are gonna conflict, and share the same log file.
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 locating RetroArch's existing save-per-content-directory handling and the runtime-log storage entry points; the issue names no files or tests. Compare those paths with the current per-core and aggregate behavior. Done means runtime logs are separated by content directory without splitting playtime across cores or causing same-named games from different systems to conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100