ModernUI is a comprehensive UI engine and desktop application framework & runtime
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
BloCamLimb/ModernUI 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 BloCamLimb/ModernUI 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 7.5 places BloCamLimb/ModernUI in the D tier.
The external contributor pull request merge rate for BloCamLimb/ModernUI is 0.0%, based on public PR activity from non-core contributors.
BloCamLimb/ModernUI currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in BloCamLimb/ModernUI. Reviews community pull requests with focus on project quality.
Discussions in BloCamLimb/ModernUI 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/BloCamLimb/ModernUI?utm_source=github&utm_medium=badge)
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.
Describe the bug During the game, everything is fine, but if you open the block menu, pause, advancements and other screens, the player's level number remains visible when it should be either darkened or completely hidden (probably) To Reproduce Steps to reproduce the behavior: Open any game&block menu See bug Expected behavior Vanilla darkening/blurring of the player level number was expected when opening other menus. Screenshots Environment Mod Version: 3.13.0.1 NeoForge Version: 21.1.233 Operating System: Windows 10 LTSC 22H2 x64 Graphics Card: nVidia GeForce GT240 (OGL3.3/DX10) Other Mods: Sodium 0.8.12-beta.1; Imediately Fast 1.6.10; Ferrite Core 7.0.3; Modern Fix 5.27.14; Mekanism 10.7.19.85
Describe the bug 1.21.1 neoforge with the mod ez actions，some parts will be wrongly blurred，may the overrideVanillaBlur of modern ui mistakenly identifying some parts as background ，I am not sure about the attribution of the problem, so both authors raised the issue To Reproduce open the menu of ez actions to see Expected behavior should not be blurred Screenshots Environment Mod Version: 3.12.0.2 Forge Version: 1.21.1 neo Operating System: windows Graphics Card: Other Mods: EZ actions
Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Enter the game Open Iris and enable shaders (ComplementaryUnbound_r5.7.1 EuphoriaPatches_1.8.2) Open the user interface (such as the menu or the inventory opened with "E") Severe frame drops occur (1FPS or 2FPS) Expected behavior There shouldn't be serious lag when opening these interfaces. Screenshots This is the list of mods I think it's these two factors affecting the frame rate Information Operating System: Windows 11 Minecraft Version: 1.21.1 Modern UI: 3.12.0.2 Fabric Loader: 0.18.4 Iris Version: 1.8.8 mc1.21.1 Sodium Version: 0.6.13 mc1.21.1 CPU: 12th Gen Intel(R) Core(TM) i5-12490F Graphics Card: NVIDIA GeForce RTX 2060 GPU Driver: 591.86 Operating System: Windows 11 98071561246eb07cb03726a30ba5268c.mp4
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 BloCamLimb/ModernUI, 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 BloCamLimb/ModernUI 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.
BloCamLimb/ModernUI 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 7.5 places BloCamLimb/ModernUI 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, BloCamLimb/ModernUI 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 BloCamLimb/ModernUI 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.