libretro / libretro/RetroArch

[Feature Request] "Content Resume": option to Auto-load last core and content upon retroarch start

Open
#18,599 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

It would be very convenient if the user could enable an option that makes it so that Retroarch, as soon as it's started, automates loading the most recently played content. That paired with auto-load state would be an immense QoL setting for quickly resuming play, especially in long games that take multiple play sessions to beat. While some frontends and retro handhelds provide that functionality externally, I'd love to be able to use that with Steam Retroarch without the need of an external frontend.

Now, there might be some concerns with such an option being problematic if the user tries to load a content that's crashing, causing them to become "stuck", always crashing when trying to start retroarch and unable to change the option. Obviously that could be fixed by just editing the .ini manually to disable the proposed setting temporarily, but that's not ideal. I can think of some possible ways to avoid this:

Option 1: instead of straight up loading the content without asking anything, just start with a "Want to Resume Last Played Content?" YES/NO prompt. Still faster than navigating to the recent entries playlist, picking the content, hitting play etc.

Option 2: Make it a command line argument instead of a GUI acessible option. That way, the user can add that as a launch parameter in steam retroarch properties and remove it they're stuck with a crashing content. Would hide it away from user that are more likely to get stuck with such options.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by mapping RetroArch's startup flow and recent-content loading behavior, then resolve whether resuming should be automatic, prompted, or command-line-only. Done requires an agreed design, safe recovery from crashing content, and tests covering the selected 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
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.