TASEmulators / TASEmulators/BizHawk

[Core Port Req.] eien's quickerNES

Open
#3,848 22 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Core: QuickNes Repro: Fixed/added in 2.10 Request: Feature/Enhancement Request: New core/port/re-port
Dominant language
C#
Stars
2.8k
Forks
468
No merged PRs in 30d

Description

Merged on 2024-03-22 and released with 2.10.

Open tasks:

  • re-triage remaining issues in the Core: QuickNes label (at the time of the merge, there were 3)
    • also decide whether to continue using that label or create a new one (doesn't matter, just keep it -- Morilli)
  • update build scripts (done with https://github.com/TASEmulators/BizHawk/commit/d17352a20411a98c76494006d94d9193cbc95a68 ?)
  • add Virtual Pads for Arkanoid peripherals (may be able to re-use NesHawk's)
  • update Nix expression unmanaged deps aren't split out so there's nothing to do
  • Implement additional services:
    • IDebuggable.SetCpuRegister
    • IInputCallbackSystem (IInputPollable.InputCallbacks)
    • IMemoryCallbackSystem (IDebuggable.MemoryCallbacks)
    • IRegionable
    • IRomInfo

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 reviewing the remaining checklist for Core: QuickNes and the existing Core: QuickNes label, then compare the Arkanoid peripheral work with NesHawk's Virtual Pads. Inspect the listed interfaces—IDebuggable.SetCpuRegister, IInputCallbackSystem, IMemoryCallbackSystem, IRegionable, and IRomInfo—and confirm the remaining scope with maintainers. Done means the unchecked services and Arkanoid Virtual Pads are implemented and the checklist can be closed.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.