Builds
Build and download an artifact
Build saved source to produce an installable artifact: a JAR for a Paper plugin or Fabric mod, or a validated ZIP for a datapack. Launch a deployment to run the artifact on a temporary Minecraft server for testing.
Prepare the source
Section titled “Prepare the source”- Wait for generation to finish.
- Resolve pending change review.
- Save manual edits.
- Check that required dependencies are present and correct.
- Confirm the project’s target and requested behavior.
Manual builds do not have a separate credit deduction. Requesting a repair for a failed build uses credits like other chat requests.
Run a build
Section titled “Run a build”- Open Build history from the project.
- Choose Build now.
- Wait for the recorded build result.
- Inspect the successful artifact or failure details.
You can also use /build from the chat command picker. Generation may already have produced a build, so check the latest entry before running another.
If Buildryn reports the project is up to date, the current saved state does not require a new build under its build checks. Check that you saved the edits you wanted to build.
Read the build history
Section titled “Read the build history”Entries identify the build number, source/version information, result, and available actions. An entry may offer download, rebuild, error-log download, source restore, or a security report depending on its state.
Keep the build number with your testing notes. “The latest version failed” becomes ambiguous as soon as another build runs; “Build #12 fails after /daily” is much easier to investigate.
A successful build confirms compilation or packaging. It does not establish that commands, permissions, persistence, or gameplay are correct.
Download a successful artifact
Section titled “Download a successful artifact”- Locate the successful build you want.
- Use its download action.
- Confirm the file extension and version.
- Keep the artifact with its target-version and dependency requirements.
Download a JAR for a plugin or mod, or a ZIP for a datapack. An individual file downloaded from the editor is source content, not the packaged build artifact.
Artifact limits are 10 MB for the Free plan, 50 MB for Basic, and 100 MB for Pro, using the project owner’s plan. If the artifact exceeds the limit, review included dependencies/resources or choose a suitable plan.
Diagnose a failed build
Section titled “Diagnose a failed build”- Open or download the build’s error log.
- Find the earliest useful failure with a file path, line, missing dependency, or validation explanation.
- Use Fix error if available, or send the error in a Build request.
- State the build number and behavior you want preserved.
- Review the repair and run the build again.
Build #<number> fails with the error below.Fix the cause while keeping the existing commands and configuration compatible.<relevant error excerpt>| Error category | What to check |
|---|---|
| Java syntax or type error | Named file, symbol, and target API. |
| Dependency resolution | Dependency version, build declaration, and integration setup. |
| Missing plugin declaration | Main class, command/permission metadata, and related names. |
| Datapack validation | pack.mcmeta, target layout, and the identified data/function file. |
| Artifact too large | Included resources and dependencies, plus the owner’s limit. |
Inspect the repair to check that it fixes the cause, then retest the affected behavior.
Historical builds and restores
Section titled “Historical builds and restores”Use an older entry to rebuild or download an artifact from its recorded source commit. Historical downloads may reconstruct the artifact, so they can take time and can fail if history or compilation is unavailable.
Use Revert to this commit only when you want to replace current source with that historical state. Follow history and recovery before doing so.
Test and release
Section titled “Test and release”- Inspect eligible security details.
- Launch the latest successful artifact using the deployment controls.
- Check the artifact label on the deployment dashboard.
- Test your acceptance checklist in Minecraft.
- Download the tested build and install it in your destination environment.
If you edit source after deployment, rebuild and deploy the new artifact. Restarting an old deployment keeps its existing artifact.