libretro / libretro/RetroArch

Deleting cheats

Open
#12,915 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

Cheat codes delete bug

[Description of the bug]

when you delete a cheat you get his

1

Expected behavior

to delete the code

[What you expected to happen]

to delete the code

Actual behavior

when deleting a code you get N/A

[What is actually happening]

Steps to reproduce the bug
  1. [First step] put in a chat
  2. [Second step] delete the cheat
  3. [and so on...] you will see the N/A
Bisect Results

[Try to bisect and tell us when this started happening]

i'm not sure this is my first time deleting a cheat

Version/Commit

You can find this information under Information/System Information

  • RetroArch: [version/commit]
    1.9.8
Environment information

Windows 10

  • OS: [The operating system you're running]
  • Compiler: [In case you are running local builds]

Also it seams to delete other codes to when you try to delete the N\A

here is a video I made of the problem i just notice it deletes all my codes if I try to delete the N/A

https://www.youtube.com/watch?v=nn721cpr_6g

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 cheat deletion behavior in RetroArch 1.9.8 on Windows 10, following the provided steps and video. Trace the cheat deletion flow and verify that deleting the N/A entry removes only the selected code; done means other cheat codes remain intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
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.