A browser based Pokémon fangame heavily inspired by the roguelite genre.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 73%
Response Time: -
First Timer Success: 67%
pagefaultgames/pokerogue has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pagefaultgames/pokerogue 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 68.7 places pagefaultgames/pokerogue in the A tier.
The external contributor pull request merge rate for pagefaultgames/pokerogue is 72.5%, based on public PR activity from non-core contributors.
pagefaultgames/pokerogue currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A browser based Pokémon fangame heavily inspired by the roguelite genre.
Strict review standards in pagefaultgames/pokerogue. 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/pagefaultgames/pokerogue?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (91% approval). Large PRs (>500 lines) take ~115 hours (33% approval). Keep your diff compact for rapid review.
No Retreat can now only be used successfully once per switch-in regardless of other statuses. Subsequent uses will cause the move to fail. Meaning if the Pokémon has been trapped by Mean Look or Jaw Lock already, it can still only successfully use No Retreat once until it gets switched out.
Is your feature request related to a problem? Please describe. With the introduction of NatDex moves, it’s apparent with Burn Up now being in learnsets again that certain Gym Leaders like Gordie will have a moveslot that does nothing. This is because Gordie Terastalizes his Coalossal (Fire / Rock) into Tera Rock, so Burn Up is unable to be used. Describe the Feature There is already code in ai-moveset-gen.ts that handles filtering of movepools and checking if a Pokemon is about to terastalize. Add a check that filters Double Shock / Burn Up from the movepool if the Pokemon is set to terastalize but not into an Electric or Fire type, respectively. Additional context No response
Bug report initiated by Discord user fabske5 Describe the bug Related Discord message Reproduction const overrides = { STARTING_WAVE_OVERRIDE: 80, ENEMY_SPECIES_OVERRIDE: SpeciesId.GUMSHOOS, BATTLE_STYLE_OVERRIDE: "double", } satisfies Partial<InstanceType<OverridesType>>; Has to be a non trainer boss Additional context If the boss is the same species and should have 2 segments, neither pokemon has a boss bar due to having the same bst. The related code should b e here
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 pagefaultgames/pokerogue, 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 pagefaultgames/pokerogue acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.5% were successfully merged into the primary branch.
pagefaultgames/pokerogue has a recorded first-timer success rate of 66.7%. 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 68.7 places pagefaultgames/pokerogue in the Welcoming tier.
The external pull request merge rate is 72.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pagefaultgames/pokerogue currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for pagefaultgames/pokerogue 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.