libretro / libretro/RetroArch

[Steam] RetroArch should supply its own cheats database, or allow downloading it

Open
#17,101 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

I know libretro has a large database of cheats. I know the stand-alone version has an online updater that can download new assets, and new cheats. However, there is no online updater on the Steam version.

According to Gadsby, cheat files are already included with the builds. Thus, I expected to find them on the Steam release. (Unless, of course, I misunderstood the message.)

This guide on the Steam Community claims:

RA steam version by default has the cheat folder (named cht) already in the correct place and mapped correctly in directory but does not have any cheat files

Expected behavior

Upon launching the Steam release of RetroArch (on the Steam Deck), and opening a game, I'd expect to find a list of known cheats in the Cheats menu (from the Quick menu).

Actual behavior

No cheats are listed.

I can confirm the common/RetroArch/cheats/ directory exists, but it only contains empty folders.

I can confirm the common/RetroArch/database/cht/ directory does NOT exist.

Steps to reproduce the bug
  1. Install and launch RetroArch from Steam.
  2. Open a game inside RetroArch.
  3. After the game loads, open the Quick Menu.
  4. Scroll down to the Cheats menu.
  5. Try to load a Cheat File. (Even better if it would load automatically. Is it possible?)
  6. Observe how there are no cheat files available, and no way to download them.
Bisect Results

There is no bisect possible. I don't think this is related to code, but to packaging of the project. I even tried looking at some CI/CD (GitHub Actions) that would prepare the Steam version, but I found nothing.

Version/Commit
  • RetroArch: 1.19.1 0792144fe3
Environment information
  • OS: SteamOS on the Steam Deck

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 inspecting the Steam packaging configuration and the CI/CD setup mentioned in the issue. Compare common/RetroArch/cheats/ with the absent common/RetroArch/database/cht/ directory and determine how the Steam release obtains assets. Done means the Steam build supplies usable cheat files or provides a working way to download them.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, release
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.