Environment information, runtime evidence, checks and reports without leaving Minecraft.

GradleMC v1.1.0 — rebuilt in Kotlin

Minecraft 1.20.1  •  Forge  •  Java 17 runtime  •  Kotlin for Forge required

gradlemc-1.1.0-forge-1.20.1.jar

GradleMC v1.1.0 marks a major internal transition. The Forge 1.20.1 edition has been rebuilt in Kotlin, replacing the previous Java implementation.

• GradleMC's own source implementation is now Kotlin.
• The previous Java GradleMC implementation has been removed from this release.
• The mod now depends on Kotlin for Forge to provide its Kotlin runtime and Forge integration.
• The current Forge 1.20.1 development line uses Kotlin for Forge 4.12.0.
• Minecraft 1.20.1 itself still runs on Java 17. The Kotlin rewrite does not mean Java should be removed from your Minecraft installation.

What is GradleMC?

Modded Minecraft can fail in spectacularly unhelpful ways. Low FPS, stuttering, memory pressure, overloaded worlds, strange mod combinations, server tick problems and unstable configurations often produce the same diagnostic masterpiece:

"It feels laggy."

That is not evidence.

GradleMC gives players, modpack creators, server owners, testers and developers a structured way to inspect a Minecraft instance before changing random settings or deleting half the modpack.

It gathers relevant local information, measures bounded runtime signals, performs rule-based checks and turns the available evidence into readable diagnostic output.

The workflow

01 — Inspect

Review Minecraft, mod loader, Java runtime and GradleMC information alongside loaded mods, configurations, paths, memory state and relevant environment details.

02 — Measure

Observe supported runtime signals such as FPS, frame behaviour, memory pressure, TPS/MSPT, entities, block entities, world-generation activity and bounded profiling information.

03 — Diagnose

Use local rule-based Smart Diagnostics to connect available evidence, identify suspicious conditions, expose missing information and produce prioritised guidance.

04 — Export

Generate readable reports and diagnostic evidence for troubleshooting, bug reports, controlled comparisons, support requests and modpack maintenance.

Core capabilities

Diagnostics control centre

• Open the in-game GradleMC interface using /gradlemc gui or the configurable keybind.
• Access diagnostics, runtime information, reports, performance tools and supported configuration controls from one interface.
• Inspect the current state of the instance without leaving Minecraft.

Environment and mod inspection

• Minecraft, loader, GradleMC and JVM/runtime information.
• Operating-system and environment context.
• Loaded-mod summaries and inspection tools.
• Configuration, report and other relevant local paths.
• Heap and JVM memory information.

Performance evidence

• Current FPS and optional average FPS information on supported clients.
• Bounded timed FPS tests.
• TPS/MSPT-related observations where supported.
• Memory-pressure and runtime-health signals.
• Entity and block-entity observations.
• World-generation activity and pressure indicators.
• Lightweight bounded performance sampling.

Smart Diagnostics

• Local rule-based diagnostic scoring.
• Prioritised diagnostic advice.
• Supporting evidence and context.
• Identification of incomplete or missing evidence.
• No generative AI and no remote inference.

Reports and troubleshooting evidence

• Readable locally generated diagnostic reports.
• Recent-report discovery through supported commands and interfaces.
• Performance and diagnostic summaries.
• Exportable evidence for bug reports and support requests.
• TXT and JSON output where supported by the installed build.

GradleMC uses deliberately bounded diagnostic sampling. It is a troubleshooting utility, not async-profiler wearing a Minecraft skin.

Client and server

Client

Install GradleMC on the client for features such as the diagnostics interface, configurable keybind, optional overlay, FPS information, timed FPS testing and client-side environment evidence.

Server

Supported server-side functionality can include commands, runtime observations, memory and environment information, loaded-mod inspection, performance evidence, reports and Smart Diagnostics.

For investigations that require evidence from both sides, install the appropriate GradleMC build and its required dependencies wherever that build is intended to run.

Installation — Forge 1.20.1 v1.1.0

1. Install Minecraft Java Edition 1.20.1 with a compatible Forge 1.20.1 installation.
2. Use Java 17 for Minecraft 1.20.1.
3. Download gradlemc-1.1.0-forge-1.20.1.jar.
4. Download Kotlin for Forge.
5. Place both required mod jars in the instance or server mods folder.
6. Launch Minecraft.
7. Run /gradlemc to inspect the command tree supplied by the installed GradleMC build.

Use the exact build

Minecraft versions and mod loaders are not interchangeable.

A Forge build is not a Fabric build. A Fabric build is not a NeoForge build. A 1.20.1 jar does not magically become a 1.21 build because its filename has been edited.

Always check the GradleMC Files page and choose the file matching your Minecraft version and loader.

Quilt support has ended

Maintaining another loader is not free. Every supported target multiplies compatibility work, testing and opportunities for something to catch fire in a completely loader-specific way. Development effort is better spent on the GradleMC versions people are actually using.

Release lines

GradleMC has been published for multiple Minecraft versions and mod loaders. The Files page remains the source of truth for builds that are actually available.

Minecraft 1.20.1

Java 17  •  loader-specific builds

Minecraft 1.21.11

Java 21  •  loader-specific builds where published

Minecraft 26.1.2

Java 25  •  loader-specific builds where published

Quilt: discontinued. No new GradleMC Quilt releases are planned.

Essential commands

GradleMC commands are lowercase. Exact command availability can vary by release, environment, permissions and client/server side.

• /gradlemc — inspect the command tree available in your build.
• /gradlemc gui — open the diagnostics interface.
• /gradlemc status — show a compact diagnostic status summary.
• /gradlemc version — show GradleMC and environment version information.
• /gradlemc memory — inspect JVM memory information.
• /gradlemc check — run available local diagnostic checks.
• /gradlemc testfps start <seconds> — begin a bounded client FPS test.
• /gradlemc testfps stop — stop an active FPS test.
• /gradlemc perf start <seconds> — start a supported bounded 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 diagnostic guidance.

Additional commands may exist for performance testing, reports, profiling, loaded mods, entities, world generation and other diagnostic systems. Use /gradlemc instead of assuming that every historical command exists in every build.

Generated files

GradleMC stores its local diagnostic data beneath:

<gameDir>/gradlemc/

Depending on the installed release and action used, this directory can contain diagnostic reports, exports, profiling information, issue evidence, configuration-related files and other GradleMC output.

Review diagnostic files before sharing them. Reports can contain local paths, Java/JVM information, loaded mod names, loader details, instance information and other system context.

GradleMC does not automatically upload these reports.

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 automatic transmission of generated troubleshooting evidence.
• No broad scanning of unrelated private files.
• Your generated evidence remains local until you choose to share it.

Smart Diagnostics is not generative AI. It is a local rule-based diagnostic system designed to evaluate available GradleMC evidence and return structured guidance.

What GradleMC is not

• Not an FPS booster: GradleMC measures and diagnoses performance; it does not manufacture additional GPU horsepower.
• Not a crash-fixing bot: it can expose useful evidence, but it cannot automatically repair every incompatible or broken modpack.
• Not a replacement for performance mods: it does not replace Sodium, Embeddium or careful configuration.
• Not a full low-level profiler: advanced CPU, allocation or tick investigations may still require tools such as Spark, Java Flight Recorder, VisualVM or async-profiler.
• Not a universal jar: use the correct Minecraft-version and loader-specific build.
• Not a Gradle replacement: GradleMC and the Gradle Build Tool are separate projects.
• Not a Bedrock Edition tool: GradleMC targets supported Minecraft Java Edition releases.

Support and development

Source code and project documentation are available from the GradleMC GitHub repository.

For reproducible GradleMC bugs, use the GitHub issue tracker.

Useful reports should include the exact Minecraft version, mod loader, Java runtime, GradleMC version or jar filename, reproduction steps and relevant reviewed diagnostic evidence.

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