Skip to content

Features

Everything between the idea and the running plugin.

One workspace for planning, writing, building, fixing and shipping Minecraft plugins. Each capability below is a screen you can use today.

01

AI project generation

Start from a sentence. ChunkMint plans the plugin first, so you can correct the approach before any code is written.

  • Plan, Build, Fix and Explain modes
  • Targets Paper, Purpur, Velocity, Folia or BungeeCord
planPlan mode

You

Dodaj system /daily z cooldownem 24h zapisanym po restarcie.

  1. 01Create DailyCommand
  2. 02Create CooldownRepository
  3. 03Persist state
  4. 04Add permissions
  5. 05Add localized messages

02

Context-aware modifications

Follow-up prompts change the project you already have. The agent reads the existing files and edits them instead of regenerating from scratch.

  • Multi-file changes in one step
  • Knows the dependencies already declared
DailyRewards · paper 1.21.8app.chunkmint.dev

You

Dodaj cooldown 30 sekund do /daily

AI

I'll update DailyCommand and introduce a persistent cooldown service so the timer survives restarts.

Changes
+CooldownService.java+15−0
~DailyCommand.java+13−2
~messages_pl.yml+1−0
Build #41Ready

03

A real file system

The workspace is a normal plugin project: source, plugin.yml, message bundles and a Gradle build. Open any file and read it.

  • Java, YAML and Kotlin build scripts
  • Read-only viewer, edits go through review
DailyRewards · paper 1.21.8app.chunkmint.dev

You

Dodaj cooldown 30 sekund do /daily

AI

I'll update DailyCommand and introduce a persistent cooldown service so the timer survives restarts.

Changes
+CooldownService.java+15−0
~DailyCommand.java+13−2
~messages_pl.yml+1−0
Build #41Ready

04

Diff review

Every change arrives as a diff with added and removed lines. Accept or reject per file.

  • Per-file accept and reject
  • Rejecting a generated file removes it
src/commands/DailyCommand.java+4 −1
12 public final class DailyCommand implements CommandExecutor {
13+ private static final long COOLDOWN_SECONDS = 24 * 60 * 60;
14 private final CooldownRepository cooldowns;
27− rewards.grant(player);
27+ if (cooldowns.remaining(player) > 0) return deny(player);
28+ rewards.grant(player);
29+ cooldowns.start(player, COOLDOWN_SECONDS);
RejectAccept

05

Snapshots

A snapshot is saved after each successful build. Compare, or restore an earlier version as a new snapshot.

  • History is never rewritten
  • Restore in one click
history3 snapshots
  1. v18CURRENT

    2 min ago

    Cooldown persistence

    Restore Compare
  2. v17

    12 min ago

    Initial implementation

    Restore Compare
  3. v16

    15 min ago

    Added configuration

    Restore Compare

06

Automated builds

Each generation is compiled in an isolated environment and checked before it is offered to you.

  • Compile, package and artifact, recorded per build
  • Java version chosen from the Minecraft version
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)

07

Build repair

When a build fails or the plugin does not load on the test server, the error is analysed, patched, rebuilt and tested again within a bounded number of attempts.

  • The failed step and short error are always shown
  • One click to run Fix with AI

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

08

Artifact management

Successful builds keep their .jar so you can download an earlier version. Retention depends on your plan.

  • Named, versioned artifacts
  • Failed builds show why there is none
artifacts
  • #41chunkmint-auctions-1.0.0.jar38 KB
  • #39chunkmint-auctions-1.0.0.jar31 KB
  • #40no artifactfailed at Compile

09

Managed Minecraft test environments

Every build can be launched on a temporary Paper or Purpur server that ChunkMint starts and removes for you. Nothing to connect or install.

  • Temporary Paper and Purpur instances
  • The artifact is installed automatically
  • Startup logs analysed, then automatic cleanup
  • No user infrastructure required
pipelinetemporary environment
  1. 01Build
  2. 02Create test environment
  3. 03Install plugin
  4. 04Start Paper/Purpur
  5. 05Analyze logs
  6. 06Test passed
test run #42Passed
  • Provisioning environment
  • Installing plugin38 KB
  • Starting MinecraftPurpur 1.21.8
  • Plugin loadenabled
  • Log analysis0 errors
  • Runtime validation

Environment destroyed · 1m 12s

10

Runtime validation

Compile validation shows the code builds. Runtime validation shows the plugin actually loads on a running server. They are reported as separate results.

  • Compile validation: compile, package, artifact
  • Runtime validation: install, boot, plugin load, log analysis
build #41Ready
  • Compile
  • Package
  • Artifact
  • Runtime testPassed
View test

11

Test runs

Each run is recorded with its Minecraft and Java version, lifecycle, console log and result, so a failure can be read and fixed.

  • Queued through passed, failed, timed out or cancelled
  • Environment destroyed after every run
AuctionHouse · Run #46Booting

Purpur 1.21.8 · Java 21 · temporary environment

DailyRewards · Run #45Passed

Paper 1.21.8 · Java 21 · 1m 12s

CrateKeeper · Run #41Failed

Paper 1.20.6 · Java 21 · missing dependency

12

Usage controls

Plans include AI compute credits. You can see what was spent on generation, fixes and explanations.

  • Credits track model compute
  • Effort levels trade depth for cost
usagethis cycle

2,760 credits left

1,240 / 4,000

  • Generation

    780

  • Build fixes

    310

  • Explain, plan

    150

Build your next Minecraft plugin.

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

Describe what you want to build...Start building