libretro / libretro/RetroArch

Entries above 200 in the "favorites" list get deleted if you generate a default cfg.

Open
#16,735 1 comment 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

The default number of maximum items in the favorites list is 200. You can change this to a bigger number, which i did. I currently have 247/250 items. But one day i needed to load a fresh, default cfg file for troubleshooting something unrelated. This caused the last 47 entries in the playlist file to get deleted, something i only noticed after a while when i saw all the games after a certain letter missing.

Expected behavior

Not sure but modifying the file itself like that, without any warning, shouldn't be the way i think. Maybe RA could just show the first 200 entries in the menu by default, even if there are more and not delete the excess ones from the actual file? Depending on how big the playlist file is it can be a ton of entries lost if you are not aware of this and not make a backup. I assume this applies to other playlists as well.

Version/Commit

1.18.0

Environment information

Windows 10

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 reproducing the issue with a favorites or playlist file containing more than 200 entries, then generate a default cfg and compare the file before and after. Investigate the interaction between the configured maximum and playlist persistence. Done means generating a default cfg no longer silently deletes excess entries, or clearly warns before changing them.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.