Skip to content

Builds

Every generation is compiled before you see it.

Generated code goes through the same steps a developer would run locally, inside isolated build environments, with the result recorded.

  1. 01Generate6 files
  2. 02CompileJava 21
  3. 03Package
  4. 04Artifact.jar
  5. 05Runtime testPaper 1.21.8

Isolation

Isolated build environments.

Each build runs in its own environment with no access to other workspaces. Nothing is built on your machine, and generated code only ever runs on a temporary ChunkMint test server, never on yours.

  • No local JDK or Gradle install
  • One build cannot see another workspace's files
build #41
> ./gradlew build
:compileJava
:processResources
:classes
:shadowJar
:jar
BUILD SUCCESSFUL in 14s
target Paper 1.21.8 · Java 21
artifact chunkmint-auctions-1.0.0.jar (38 KB)

Toolchain

Gradle or Maven, with the right Java.

Projects use a standard build script. ChunkMint picks the Java toolchain from the Minecraft version you target, so a 1.21 plugin is not compiled for Java 11.

MinecraftJava toolchain
26.1 and newerJava 25
1.20.5 to 1.21.xJava 21
1.18 to 1.20.4Java 17
1.16.5Java 11

Runtime test

A green build is not a working plugin.

Compiling and packaging prove the code builds. A separate runtime test starts a temporary Paper or Purpur server, installs the .jar and checks that the plugin loads. The two are reported separately, because a plugin can compile cleanly and still fail on startup.

  • Build and runtime test have their own status
  • The failing step and the error are always shown
  • The environment is destroyed after the test
  • CompileJava 21
  • Package
  • Artifact created
  • Test server startedPaper 1.21.8
  • Plugin installed
  • Plugin loaded
  • Startup log validation

Build to test

Every artifact links to its test.

Each build lists compile, package and artifact, then the result of its runtime test, with a link to the full test run.

build #41Ready
  • Compile
  • Package
  • Artifact
  • Runtime testPassed
View test

Logs

When it fails, you see why.

A failed build shows the step that failed, a short error and the location. The full compiler output is there when you need it.

build #40
> ./gradlew build
:compileJava
src/services/RewardService.java:9: error: cannot find symbol
VaultEconomyProvider provider;
^ symbol: class VaultEconomyProvider
BUILD FAILED in 6s
failed step Compile

Repair

Automatic repair, with limits.

Fix with AI sends the error and affected files back to the agent, applies a patch, rebuilds and tests again. This covers compile errors and plugin-load failures. Attempts are bounded so a stuck build stops and reports.

01Test failed

NoClassDefFoundError
net/milkbowl/vault/economy/Economy

found on the test server at plugin load

02Analyze

Vault is used but not declared as a dependency.

03Patch

  • ~ plugin.yml
  • ~ build.gradle.kts

04Re-test

Test run #47 passed

1 repair attempt

Artifacts

A .jar you can download.

Successful builds keep their artifact with the build number. Download it and install it on any compatible server. Each artifact shows the result of its runtime test.

artifacts
  • #41chunkmint-auctions-1.0.0.jar38 KB
  • #39chunkmint-auctions-1.0.0.jar31 KB
  • #40no artifactfailed at Compile

Build your next Minecraft plugin.

Describe it. Build it. Test it. Download the .jar.

Describe what you want to build...Start building