Question: Preferred approach for large DuckStation-to-RetroArch PSX cheat merge

[donmega]

final.txt

Hi! I’ve prepared a conversion/merge of DuckStation PSX cheats into the existing RetroArch PSX cheat files in this repo.

The generated output is quite large: it converts the DuckStation .cht files to RetroArch format, merges them with existing matching cheat files where possible, creates new files where no matching file exists, and removes duplicate cheats during the process.

I’ve attached the conversion/merge log so you can see what would be created, merged, and de-duplicated.

Before opening a large PR, what would you prefer?

• One single PR with the full converted set
• Several smaller PRs split alphabetically or by region
• Only merging cheats into existing files first, leaving new files for a separate PR
• A different naming or formatting approach

Happy to adjust the output to match the repo’s preferred style.

[donmega]

Here is the newest version, i have fixed the filenames.

final5.txt

[RobLoach]

One big one should be fine. What do you see as the risks of adopting into all in one?

[donmega]

Thanks! A single PR works for me.

The main risks I see are:

• The diff will be very large, so review may be harder.

• Some DuckStation files are named by GameID while the RetroArch files are named by game title, so there is a small risk of an incorrect merge if a title match is wrong.

• Some newly created files may still need filename/style review, especially for regional variants, revisions, demos, and non-ASCII titles.

• Duplicate removal is based on normalized cheat codes, so there is a small chance that two cheats with the same code but different descriptions/intent could be collapsed.

• I have not personally tested every cheat in-game, only the conversion/formatting and de-duplication.

To reduce the risk, I can include the conversion log, keep the conversion script available for review.