A multiplatform server-side implementation of HUD in Minecraft, supporting Bukkit(with Folia), Velocity, and Fabric.
C-Rank Grade: D (Risky) - 21/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
toxicity188/BetterHud has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in toxicity188/BetterHud 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 21.3 places toxicity188/BetterHud in the D tier.
The external contributor pull request merge rate for toxicity188/BetterHud is 0.0%, based on public PR activity from non-core contributors.
toxicity188/BetterHud currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Kotlin project in toxicity188/BetterHud welcoming community pull requests and bug fixes.
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/toxicity188/BetterHud?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
My suggestion its that can be put the new sprites / atlas like this sprite:blocks:block/stone in texts.
Will there be plans to support craftengine?
Hi! I am using BetterHud for a skill HUD with many possible ability icons. Current limitation: image.name is resolved statically on config load. Conditions can choose between static entries, but image name itself cannot be selected by a placeholder. Because of that, a HUD with many ability icons needs hundreds of layout entries, one per icon/state, each with conditions. Real config impact: One skill layout has ~256 image entries. Before local optimization it had ~1200 PlaceholderAPI references. I moved the logic to native BetterHud placeholders and added tick: 3, but the layout still needs many static entries because the image name cannot be dynamic. Example of what would help: images: skill_icon: name-placeholder: "ability_[cas_hud_key:SWAP_HANDS]_color_sm" fallback: "ability_default_color_sm" x: -62 y: -59 layer: 12
I have a suggestion: right now, you can set a background with 3 images, but I think it would be cool if you could use up to 9 images. It would look something like this: Top left, top center, top right Left center, center, right center Bottom left, bottom center, bottom right 1 2 3 4 5 6 7 8 9 1222222223 4555555556 4555555556 4555555556 7888888889 It would just be handy for more dynamic text boxes so there isn’t as much pixel distortion.
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 toxicity188/BetterHud, 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 toxicity188/BetterHud acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
toxicity188/BetterHud has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 21.3 places toxicity188/BetterHud in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, toxicity188/BetterHud currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for toxicity188/BetterHud 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.