XNA / MonoGame based client for playing classic Command & Conquer games both online and offline with a CnCNet game spawner.
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 68%
Response Time: 13h
First Timer Success: 75%
CnCNet/xna-cncnet-client has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in CnCNet/xna-cncnet-client respond to incoming external pull requests in approximately 13.3 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 61.4 places CnCNet/xna-cncnet-client in the A tier.
The external contributor pull request merge rate for CnCNet/xna-cncnet-client is 67.6%, based on public PR activity from non-core contributors.
CnCNet/xna-cncnet-client currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in CnCNet/xna-cncnet-client. Reviews community pull requests with focus on project quality.
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/CnCNet/xna-cncnet-client?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~9 hours (85% approval). Large PRs (>500 lines) take ~64 hours (30% approval). Keep your diff compact for rapid review.
Description 02.05. 14:57:28.450 ***Logfile for CnCNet Client client*** 02.05. 14:57:28.453 Client version: 2026-05-02 pr/948@73874cd 02.05. 14:57:28.453 2.12.19-PullRequest0948.85+Branch.pr-948.Sha.73874cd0d621388ba249df04f446a32c13a2c000 02.05. 14:57:28.453 This is a development build of the client. Stability and reliability may not be fully guaranteed. 02.05. 14:57:28.464 Loading settings. 02.05. 14:57:28.480 Failed to load a translation file. Neither D:\SadPencil\Documents\GitHub\xna-cncnet-client\DXMainClient\bin\Debug\WindowsDX\net48\Resources\Translations\en\Yuri Theme\Translation.ini nor D:\SadPencil\Documents\GitHub\xna-cncnet-client\DXMainClient\bin\Debug\WindowsDX\net48\Resources\Translations\en\Translation.ini exist. 02.05. 14:57:28.489 Loaded translation: English 02.05. 14:57:28.499 Initializing updater. 02.05. 14:57:28.510 KABOOOOOOM!!! Info: 02.05. 14:57:28.510 Type: System.IO.IOException 02.05. 14:57:28.510 Message: The process cannot acc
Description The client may randomly crash when trying to basically just start the game. XNA Client Version 2.12.18 Steps To Reproduce Start any match, skirmish lobby is recommended. Expected Behaviour Should receive a crash error popup upon launching the match. Actual Behaviour This event may randomly occur and is not that consistent, but usually happens after a successful launch of a match. Additional Context ClientCrashLog_2026_04_22_19_18.txt Checklist The issue happens on the latest official version of XNA Client and wasn't fixed yet. I agree to elaborate the details if requested and provide thorough testing if the bugfix is implemented. I added a very descriptive title to this issue. I used the GitHub search and read the issue list to find a similar issue and didn't find it. I have attached as much information as possible (screenshots, gifs, videos, client logs, etc).
Description At present, the auto-ally menu is hidden under a small, unintuitive button. If feasible, it could be moved to be present above the map preview, see screenshot for example. Team preset selection as the first option, displaying any teaming presets saved in the map file. Dropdowns for available spots on the map to allow setting the team per spot. A button to display a menu for all of the force random options for side, colour, team and starts. When the team is set, the map number locations could display the team letter, similar to how a player's name is displayed when a spot is manually set for a player.
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 CnCNet/xna-cncnet-client, 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 CnCNet/xna-cncnet-client acknowledge new external contributions in approximately 13 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 67.6% were successfully merged into the primary branch.
CnCNet/xna-cncnet-client has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~13 hours. 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 61.4 places CnCNet/xna-cncnet-client in the Welcoming tier.
The external pull request merge rate is 67.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, CnCNet/xna-cncnet-client 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 CnCNet/xna-cncnet-client 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.