libretro / libretro/RetroArch

[Feature Request] Option to automatically pause hardcore mode when loading save states

Open
#17,203 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

There is already logic in RetroArch to automatically pause RetroAchievements hard core mode when loading save states, see here. However, since there is a warning message before, it's never reached.

I created a PR removing the warning message to automatically pause it, but since people often have keybinding for this action, it would be too easy to accidentally trigger.

Improvements to this flow would still be very useful, to avoid manually having to go in to the settings to pause hardcore mode every time you want to use save states.

I have a few suggestions for options, please comment if you have better ones:

  1. Add a new configuration option to automatically bypass the warning and disable hardcore mode
  2. Make it work the same way as the "Press again to quit...", where loading save states twice in a certain time span will pause hardcore mode for the session, and any additional loads will have no warning

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

Start by reading the existing save-state and hardcore-mode logic in command.c, along with the repeated-action flow cited in runloop.c. Compare the two proposed approaches and establish which behavior should be implemented before changing code. Done means loading save states can safely pause hardcore mode without requiring manual settings changes or accidental immediate activation.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.