libretro / libretro/libretro-database
Question: Preferred approach for large DuckStation-to-RetroArch PSX cheat merge
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 877
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 24
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached final.txt conversion/merge log and comparing its proposed output with the repository’s existing PSX cheat files. The maintainer’s decision is needed on PR size, regional or alphabetical splitting, merging versus new files, and naming or formatting; completion would be an agreed contribution plan.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100