libretro / libretro/libretro-database

(Cheats) Action Replay codes not working (tested on NES)

Open
#807 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.4k
Forks
877
Avg merge
3d 1h
Merged PRs (30d)
24

Description

Converted the Action Replay files from here: http://thealmightyguru.com/Games/Hacking/Wiki/index.php/Cheat_Archive into retroarch-format per https://retropie.org.uk/docs/Cheats/

For example, Zelda II - the Adventure of Link (USA) (Action Replay).cht:

cheats = 13

cheat0_desc = "Infinite Lives"
cheat0_code = "0700:0A"
cheat0_enable = false

cheat1_desc = "Infinite Hit Points"
cheat1_code = "0773:F8"
cheat1_enable = false

cheat2_desc = "Invulnerable"
cheat2_code = "0518:03"
cheat2_enable = false

cheat3_desc = "Infinite Magic Points"
cheat3_code = "0774:F8"
cheat3_enable = false

<snip>

Full set attached for reference and for others to test with: Retroarch NES Action Replay.zip

Retroarch parses and loads these files just fine, and each cheat can be toggled using the in-game retroarch UI. However, after enabling and applying them, none of the cheats become active, unlike the GameGenie cheats, which do work.

I'm using the master branch of retroarch and lr-fceumm.

Is there something I'm missing?

Contributor guide

No contributing guide indexed for this repository

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 attached .cht files with RetroArch and lr-fceumm, then compare their Action Replay behavior with the working GameGenie cheats. Done means identifying why the NES Action Replay codes do not activate after being enabled, and documenting or correcting the relevant cheat data if the repository is responsible.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.