TASEmulators / TASEmulators/BizHawk
Evaluate possible autopatches from bad to good firmwares
Open
Nobody has claimed this yet.
App: EmuHawk
Request: Feature/Enhancement
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
See also #2415 which this would have resolved quickly.
Contributor guide
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 reading the referenced section of src/BizHawk.Emulation.Common/Database/FirmwareDatabase.cs and the context from issue #2415. Determine which bad-to-good firmware autopatches are intended and how their behavior would be verified; the issue does not name tests or a completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100