A modding API for Minecraft: Java Edition, based on Forge
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 69%
Response Time: 13h
First Timer Success: 80%
neoforged/NeoForge has a recorded first-timer success rate of 80.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in neoforged/NeoForge respond to incoming external pull requests in approximately 13.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 63.3 places neoforged/NeoForge in the A tier.
The external contributor pull request merge rate for neoforged/NeoForge is 68.9%, based on public PR activity from non-core contributors.
neoforged/NeoForge currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in neoforged/NeoForge. Prompt code reviews with positive guidance for new contributors.
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/neoforged/NeoForge?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (86% approval). Large PRs (>500 lines) take ~62 hours (31% approval). Keep your diff compact for rapid review.
Datamap implementation for flammable block because that makes more sense then overriding the method in block class.
Minecraft Version: 26.1 and above Steps to Reproduce: Create a new instance with NeoForge in Prism Launcher. Test and write down the FPS Remove NeoForge Test and write down the FPS Description of issue: NeoForge on Minecraft 26.1 and above performs around 1.4-2.2x worse than vanilla Minecraft in Prism Launcher, this issue isn't present in the official Minecraft Launcher
Minecraft Version: 1.21.1 NeoForge Version: 21.1.234 Logs: https://mclo.gs/GGctaqs Steps to Reproduce: Install NeoForge Install a Resource Pack with panorama_overlay.png (VanillaTweaks' Menu Panorama option is easiest and most erroneous, should include one.) Weep because my perfect kitchen sink modpack has a glaring bug on startup. Description of issue: During the opening transition to the main menu, the alpha for panorama_overlay.png is just... wrong, appearing differently depending on which resource pack you use.
The network system sometimes fails, for no apparent reason, with a strange error in the logs 2026-06-13T21:55:19.861885245Z Render thread ERROR An exception occurred processing Appender DebugFile org.apache.logging.log4j.core.appender.AppenderLoggingException: java.lang.NoClassDefFoundError: Could not initialize class io.netty.channel.kqueue.Native at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:164) at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:133) at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:124) at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:88) at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:807) at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:765) at org.apache.logging.log4j.core.config.LoggerConfig.log(Logg
I am working on an in-world renderer to preview a block pattern. Similar to what multiple guidebook mods such as Patchouli and Modonomicon do. One of the users recently noticed that a specific modded block does not render. After looking at the source, it turned out they (for some reason) use bbs.json and geo.json to render a statue. It uses the ENTITYBLOCK_ANIMATED render type. Since I called the vanilla block renderer, I was a bit confused why it didn't work. Turns out BlockEntityWithoutLevelRenderer#renderByItem hardcodes all the vanilla blocks that are animated and does nothing on all modded blocks using this system. The current workaround is to check for this specific render type, fetch the BE, attach the level, and use the block entity render dispatcher to render it manually, which requires caching the BE and causing potential leaks if you don't clear the cache in something like the level unload event. Wouldn't it be reasonable to add some kind of registration for these blocks tha
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 neoforged/NeoForge, 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 neoforged/NeoForge acknowledge new external contributions in approximately 13 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 68.9% were successfully merged into the primary branch.
neoforged/NeoForge has a recorded first-timer success rate of 80.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 63.3 places neoforged/NeoForge in the Welcoming tier.
The external pull request merge rate is 68.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, neoforged/NeoForge currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for neoforged/NeoForge 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.