Test environments
Build it. Boot it. Join it.
ChunkMint launches your plugin on a temporary Minecraft server and gives you a private connection address, so you can test the feature in-game before downloading the final .jar. No SSH, FTP or setup.
Purpur 1.21.8 · Java 21 · temporary environment
Paper 1.21.8 · Java 21 · 1m 12s
Paper 1.20.6 · Java 21 · missing dependency
Lifecycle
Built. Booted. Tested.
ChunkMint does not stop after generating code. Your plugin is compiled and launched inside a temporary Minecraft server so startup and plugin-load errors can be detected before you download it.
- Environment created for the run, destroyed after it
- Logs stream into the workspace while it runs
- Failures go back to the AI with the exact error
- 01Build
- 02Create test environment
- 03Install plugin
- 04Start Paper/Purpur
- 05Analyze logs
- 06Test passed
- Provisioning environment
- Installing plugin38 KB
- Starting MinecraftPurpur 1.21.8
- Plugin loadenabled
- Log analysis0 errors
- Runtime validation
Environment destroyed · 1m 12s
What it does
Exactly what plugin validation needs.
Live plugin testing, not Minecraft hosting: whitelisted test players only, no permanent worlds, no public listing and no server settings to manage.
- Temporary Paper and Purpur
- A fresh instance for every run, on the Minecraft and Java version your project targets.
- Artifact installed for you
- The built .jar is placed in the plugins folder automatically. Nothing to upload.
- Startup logs analysed
- Exceptions, missing dependencies and load errors are picked out of the console output.
- Plugin-load validation
- A run passes only when the plugin actually enables on a real server.
- Join it yourself
- Open an interactive test server, add your Minecraft username and connect with your normal client. Only players you allow can join.
- Automatic cleanup
- The server, its world and its address are destroyed when the test completes or its time limit is reached.
- No infrastructure on your side
- No server connection, agent, SSH or FTP credentials, and no access to your production server.
Runtime validation
Compiling is not the same as working.
A plugin can compile cleanly and still fail on startup: a missing dependency, a wrong plugin.yml, a class the server does not provide. Runtime validation runs the plugin to find those problems.
- Reported separately from the build
- Failures show the error and the relevant log lines
| Compile validation | Does the code compile and package into a .jar?In an isolated build environment |
|---|---|
| Runtime validation | Does the plugin load and enable on a running server?In a temporary test environment |
Console
Developer-oriented logs.
Read the same output a server console would print, with ChunkMint's own lifecycle lines mixed in, and send Minecraft console commands to your test server. It is the game console only: you never get shell access to the environment.
[ChunkMint] Creating temporary test environment[ChunkMint] Installing AuctionHouse-1.0.0.jar into plugins/Starting minecraft server version 1.21.8[AuctionHouse] Enabling AuctionHouse v1.0.0Done (9.812s)! For help, type "help"[ChunkMint] Log analysis: 0 errors, 0 warnings[ChunkMint] Environment destroyed
Time limits
Short by design.
A test server lives only as long as the test needs. Session length, monthly test runtime, concurrent servers and test players depend on your plan.
- Free
- 5 min per test session
- 30 min test runtime / month1 test player1 concurrent test server
- Creator
- 15 min per test session
- 3 h test runtime / month2 test players1 concurrent test server
- Pro
- 30 min per test session
- 10 h test runtime / month5 test players2 concurrent test servers
- Studio
- 60 min per test session
- 40 h test runtime / month10 test players5 concurrent test servers
Build your next Minecraft plugin.
Describe it. Build it. Test it. Download the .jar.
Describe what you want to build...Start building