FPGA cores compatible with multiple arcade game machines and KiCAD schematics of arcade games. Working on MiSTer FPGA/Analogue Pocket
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 47%
Response Time: -
First Timer Success: 60%
jotego/jtcores has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jotego/jtcores respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 64.8 places jotego/jtcores in the A tier.
The external contributor pull request merge rate for jotego/jtcores is 47.2%, based on public PR activity from non-core contributors.
jotego/jtcores currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in jotego/jtcores. Prompt code reviews with positive guidance for new contributors.
Discussions in jotego/jtcores focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/jotego/jtcores?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (59% approval). Large PRs (>500 lines) take ~115 hours (21% approval). Keep your diff compact for rapid review.
The Toki core have a sound issue with the game’s main theme. There is a high-pitched crackling noise that is clearly audible. Strangely, the game’s other tracks do not seem to be affected. Here is the theme in question played correctly, as on the PCB: https://www.youtube.com/watch?v=J5d-D4bVIJY&list=PLErsx10Ke4uzcHIBInycHw1smZvgnkVUU&index=4 An audio crackle (not present on the PCB) can also be heard when flying enemies are destroyed only.
Did some lengthy playthroughs of the updated core today and noted 1 semi-common sprite glitch and 1 audio glitch that only happened once. The sprite glitch seems to happen only sometimes at the end of level (when the player does the little dance animation). https://neondagger.com/upload/cabal/Cabal_sprite_glitch.MOV The conditions for the glitch seem somewhat predictable but also somewhat random. It usually does not happen, but seems to happen every time at the end of Level1 boss battle (see video). I could be wrong, but I think it also is more likely to occur if the character is on the right hand side of the screen when the animation occurs. The sprite glitch is a vertical and sometimes horizontal line through the player, and sometimes even briefly flashes a garbled cluster of sprite data around where the player is. But this is only for a frame or two so I wasn't able to capture it or note the exact detail from observation alone. For the audio glitch, I wasn't recording but at one tim
NGPC Link Cable Support through MiSTer USERIO and Pocket Link Port Supported Games: https://www.mygamer.com/neogeo-pocket-color-2-player-link-cable-games-the-complete-ultimate-list/ Supposedly, NeoPop had support for the link cable: https://github.com/ONLYUSEmeFEET/NeoPop0.71-Win32-FINAL-Source-Code Some technical information: https://devrs.com/ngp/files/DoNotLink/ngpcspec.txt
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to jotego/jtcores, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of jotego/jtcores acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 47.2% were successfully merged into the primary branch.
jotego/jtcores has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 64.8 places jotego/jtcores in the Welcoming tier.
The external pull request merge rate is 47.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jotego/jtcores currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for jotego/jtcores are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.