Environment, runtime evidence, checks and recent diagnostic output—without leaving the game.

Featured release

Troubleshooting without ritual sacrifice

Modded Minecraft problems are rarely solved by deleting half the mods, changing twelve JVM arguments and hoping the loading screen feels spiritually faster.

GradleMC gives players, modpack creators, server owners, testers and developers a structured way to inspect a modded instance before changing it. It surfaces relevant environment details, observes bounded runtime signals and turns collected evidence into readable local output.

One workflow. Four steps.

Core capabilities

Diagnostics control centre

• Open the in-game interface with /gradlemc gui or the configurable GradleMC keybind.
• Access checks, runtime status, reports, overlay settings and diagnostic actions from one place.
• Use the established GradleMC interface refined for the Forge 1.20.1 v1.0.4 release.

Environment and mod inspection

• Minecraft, loader, Java and GradleMC build information.
• Loaded-mod summaries, counts, searches and inspection tools.
• Configuration, report and other relevant local paths.
• JVM memory state and useful runtime context.

Performance evidence

• Current FPS, optional average FPS and bounded timed FPS tests on supported clients.
• TPS/MSPT-related observations for supported server environments.
• Memory, entity, block-entity and world-generation pressure signals.
• Bounded tick, CPU-lite, memory-lite and combined profiler summaries.
• TXT and JSON output for review and comparison.

Smart Diagnostics

• Local rule-based diagnostic scores and prioritised advice.
• Supporting evidence, confidence context, trends and missing-data warnings.
• Adaptive local observations without cloud inference or hidden remote processing.

Reports and issue bundles

• Readable diagnostic reports for focused troubleshooting.
• Recent-report discovery through commands and the GUI.
• Profiler summaries and locally stored profile files.
• Reviewable issue bundles for support requests and reproducible bug reports.

GradleMC profiling is intentionally bounded and transparent about its limits. It is not pretending to be async-profiler in a trench coat.

Improved in v1.0.4

• Improved FPS measurement consistency across the overlay and timed FPS tests.
• Added independent controls for current FPS, average FPS and GradleMC overlay branding.
• Made the GradleMC overlay label optional and disabled by default.
• Fixed content overlap and usability problems in the Quick Actions tab.
• Reduced duplicated FPS and render measurement work.
• Moved runtime sampling toward safer tick-driven measurement.
• Improved client and integrated-server performance data coordination.
• Strengthened diagnostic validation and internal self-test coverage.

Client and server roles

Install on the client for

The diagnostics GUI, configurable keybind, optional overlay, current and average FPS information, timed FPS tests and client-side environment context.

Install on the server for

Server commands, permission-controlled tests, TPS/MSPT observations, memory and environment reports, loaded-mod inspection, world-generation observations, profiling, issue bundles and Smart Diagnostics summaries.

Installation

1. Open the GradleMC Files page.
2. Choose the file matching your exact Minecraft version and loader.
3. Use the Java version required by that Minecraft release.
4. Place the downloaded jar in the instance or server mods folder.
5. Launch the client or server.
6. Run /gradlemc to inspect the command tree available in that build.

Supported release lines

GradleMC is published for multiple Minecraft and loader combinations. Availability varies by release line, so always use the CurseForge Files page as the source of truth for currently published builds.

Minecraft 1.20.1

Java 17  •  matching loader-specific files

Minecraft 1.21.11

Java 21  •  matching loader-specific files

Minecraft 26.1.2

Java 25  •  matching loader-specific files

Essential commands

Commands are lowercase. Permissions, environment and side availability still apply.

• /gradlemc — show the installed build’s command help.
• /gradlemc gui — open the in-game diagnostics interface.
• /gradlemc status — show a compact diagnostics summary.
• /gradlemc version — show GradleMC, Minecraft, loader and Java context.
• /gradlemc memory — inspect JVM memory information.
• /gradlemc check — run local environment and stability checks.
• /gradlemc testfps start <seconds> — begin a bounded client FPS test.
• /gradlemc testfps stop — stop the active FPS test.
• /gradlemc perf start <seconds> — begin a bounded server performance sample.
• /gradlemc export — export local troubleshooting evidence.
• /gradlemc reports latest — locate the newest generated report.
• /gradlemc smart score — inspect the current Smart Diagnostics score.
• /gradlemc smart advice — inspect prioritised local diagnostic guidance.

Additional commands may be available for profiling, loaded mods, entities, world generation, reports, issue bundles, rules and other diagnostic systems. Use /gradlemc to inspect the command tree supplied by your exact build.

Reports and generated files

GradleMC stores its local diagnostic output beneath:

<gameDir>/gradlemc/

Depending on the installed build and action used, this can include diagnostic reports, exports, issue bundles, profiler output, local rules and supporting evidence.

Local by design

• No behavioural telemetry.
• No analytics tracking.
• No cloud AI or LLM integration.
• No hidden remote diagnostic inference.
• No automatic report upload.
• No broad scanning of unrelated private files.
• Generated evidence remains local until you choose to share it.

Smart Diagnostics is not generative AI. It is a local rule-based system that evaluates available GradleMC evidence, identifies missing information and produces scored, prioritised guidance.

Honest limitations

• Not a crash-fixing bot: GradleMC can expose useful evidence; it cannot automatically repair every broken modpack.
• Not an optimisation mod: it measures performance but does not replace Sodium, Embeddium or careful configuration.
• Not a deep-profiler replacement: difficult CPU, allocation or tick investigations may still require Spark, VisualVM, Java Flight Recorder, async-profiler or another specialist tool.
• Not a universal jar: every loader and Minecraft release requires its matching build.
• Not a Bedrock tool: GradleMC targets supported Minecraft Java Edition releases.

Support and project information

Visit the GitHub repository for source code, project documentation and development information.

Report reproducible GradleMC problems through the GitHub issue tracker. Include the exact Minecraft version, loader, Java version, GradleMC jar filename, reproduction steps and relevant reviewed report snippets.

GradleMC is an independent Minecraft project. It is not affiliated with, endorsed by or part of Gradle, Inc. or the Gradle Build Tool, and it does not replace Gradle.

Apache-2.0 • CurseForge Project ID 1585182 • Minecraft Java Edition • Client and server