Skip to content
BlogStart for free

Builds

Install a tested build

Download the successful artifact you tested, then install it in an environment that matches the project type, Minecraft version, and dependencies. Keep a copy of the previous working artifact and back up persistent server/world data before replacing it.

  1. Confirm the build number and Minecraft version.
  2. Complete gameplay tests, including permissions and failure paths.
  3. Review required dependencies and eligible security findings.
  4. Download the tested artifact.
  5. Record commands, configuration, installation requirements, and known limitations.
  6. Stop the temporary test session when you no longer need it.

After testing in Buildryn’s temporary environment, install the artifact in your own server or world.

  1. Stop the destination Paper server using its normal shutdown procedure.
  2. Check that its Minecraft/Paper version matches the build’s target.
  3. Put the downloaded plugin JAR in that server’s plugins directory.
  4. Install any required dependency plugins in compatible versions.
  5. Remove an obsolete duplicate JAR for the same plugin if you are replacing it.
  6. Start the server.
  7. Read startup logs for the plugin’s loading status and errors.
  8. Review generated configuration, adjust settings, and restart if required by the plugin.
  9. Test the commands and permissions as the intended player role.

Players do not put a Paper plugin JAR in their client mods directory. Follow your server provider’s file-management instructions if the host has a control panel.

See Paper’s official plugin-installation guide for server-side installation and loading checks.

For upgrades, check whether configuration or stored data changed. Keep existing configuration where appropriate, and add new keys following the release notes for the build so you preserve customized settings.

  1. Back up the destination world.
  2. Locate that world’s datapacks directory.
  3. Place the downloaded ZIP in it, or extract the pack into a directory whose root contains pack.mcmeta and data/.
  4. Start/reopen the world or load the pack through the environment’s supported procedure.
  5. With appropriate permissions, use /datapack list to inspect loaded packs.
  6. Check the game/server logs for format and loading errors.
  7. Run the feature’s documented initialization or tests.

On a server, the datapack belongs to the active world directory. Putting it in the plugin directory will not install it.

For a new single-player world, use the game’s datapack selection during world creation where available, then test that world before adopting it as your main save.

The archive should expose this shape at its pack root:

pack.mcmeta
data/
<namespace>/
<version-appropriate content directories>/

An extra enclosing folder can prevent recognition. Keep the metadata and data layout generated for the target Minecraft version.

A datapack can change saved player or world data. Those changes can remain after you remove the pack. Use its documented cleanup function if available and keep your backup.

  1. Close the game or stop the destination server.
  2. Install the Minecraft and Fabric loader versions required by the mod.
  3. Put the tested JAR in the mods directory on the client, server, or both, as required.
  4. Install required dependencies, including Fabric API if the mod uses it.
  5. Start Minecraft or the server, check the logs, and test the feature.

A client-only mod belongs in the game client. Follow the generated mod’s environment requirements and Fabric’s installation guides.

Symptom Check
Plugin does not load Startup error, Paper target, duplicate JAR, main-class metadata, and dependencies.
Commands are missing Plugin loading status and command declarations.
Works only for operators Permission defaults and player-role tests.
Datapack is absent from the list Pack location, ZIP structure, metadata, and target-version compatibility.
Feature still behaves like the old release Artifact version, duplicate installation, and whether the environment was restarted/reloaded as required.

Return to the project with the destination version, tested build number, reproduction steps, and relevant log excerpt. See support for a structured report.

Not an official Minecraft product. Not approved by or associated with Mojang or Microsoft.