GemRB is a portable open-source implementation of Bioware’s Infinity Engine.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 79%
Response Time: 8h
First Timer Success: 100%
gemrb/gemrb has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in gemrb/gemrb respond to incoming external pull requests in approximately 7.5 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 69.0 places gemrb/gemrb in the A tier.
The external contributor pull request merge rate for gemrb/gemrb is 79.2%, based on public PR activity from non-core contributors.
gemrb/gemrb currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in gemrb/gemrb. Ensure PR scope matches issue requirements closely before requesting review.
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/gemrb/gemrb?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (96% approval). Large PRs (>500 lines) take ~36 hours (36% approval). Keep your diff compact for rapid review.
GUICG12, GUIRECCommon, CGPortrait and others in various games all duplicate the same functionality. Rip it out into a shared python module (GUIRECCommon and PaperDoll being examples of that) and then use that instead. character generation scripts GUIRECCommon iwd2/Appearance.py Portrait
Just a heads up, I looked at pdolls.2da for BG2 for a bit, as I remember seeing this there originally, and 0x6300 through 0x6314 have the same values BG1 had before the fix. This still needs to be checked in-game ofc. 0x6315 is different: 0x6315 COFT1INV COFT2INV COFT3INV COFT4INV N Looks to be for the Half-Orc female thief. I wonder if COFT3INV & COFT4INV display correctly Originally posted by @Peppersawce in #2421 So testing is needed: creating a new (female) character and trying on armors of different kinds (none, robes, leather, chain, plate). Compare those looks to what you get in the original.
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 gemrb/gemrb, 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 gemrb/gemrb acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.2% were successfully merged into the primary branch.
gemrb/gemrb has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 69.0 places gemrb/gemrb in the Welcoming tier.
The external pull request merge rate is 79.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, gemrb/gemrb currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for gemrb/gemrb 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.