Documentation / 26.2
Docs/Install

Install

Requirements, release verification, first boot, and the Docker reference for SourbyCraft 26.2.

This page targets the current release, v26.2-r48.4. It is published and not STABLE. Install it on a test server first, with a backup of any world you care about.

Requirements

Minecraft26.2
Java25 — the runtime refuses to start on an older major version
Memory4 GB or more recommended for a small server; size to your world and plugins
NetworkRequired on first boot to fetch externalized libraries and the Mojang server jar
LicenceGPL-3.0-only
UpstreamPaper, pinned and patched by SourbyCraft

The launcher is a SourbyClip artifact. It fetches the externalized runtime libraries and the Mojang server jar, verifies them, and then starts the server. A first boot without network access will fail before the first tick.

Verify the jar

Download the jar and its checksum from the downloads page. Compare the checksum before executing anything. The release also ships an Ed25519 signature and a signed release manifest; the public key is inside the jar atMETA-INF/sourbycraft-release.pub.

verify · macOS / Linux
sha256sum -c SourbyCraft-26.2-REL.jar.sha256
# macOS
shasum -a 256 -c SourbyCraft-26.2-REL.jar.sha256
Do not skip thisA jar with a mismatched checksum is not the release. Delete it and download again rather than “testing it anyway.”

First boot

Run the jar with Java 25 from a dedicated server directory. The process stays in the foreground; use a service manager or a terminal multiplexer for a long-lived server.

first boot · shell
java -version   # Java 25
mkdir -p sourbycraft-server
cd sourbycraft-server
java -Xmx4G -jar ../SourbyCraft-26.2-REL.jar --nogui

The first boot creates the server directories and configuration. Read the console for the library fetch and verification messages. When the server reaches the first tick, connect with a 26.2 client and check the operator commands before adding plugins.

Directory layout

Build 48.4 keeps the pre-Build 49 configuration layout. Build 49 introduces renamed typed files and a TOML → YAML migration; that migration is not part of 48.4. Do not copy a Build 49 directory tree onto 48.4 and assume it is read.

config/Server and world settings. Build 48.4 retains the legacy canvas-* file names.
sourbycraft_config/Global SourbyCraft and Aurora configuration. Build 49 changes this layout.
logs/Server and runtime logs, including stall records when enabled.
plugins/Paper-compatible plugins. Read the compatibility boundary before adding region-unaware plugins.
world/World data. Back this up before changing runtime or configuration.
mods/SourbyMods ML1 artifacts, where applicable.
Build 49 is not this releaseBuild 49 configuration names and the TOML → YAML migration are documented in the workflow notes, but they are not active in 48.4. The 48.4 diagnostic reports unreadable files; it does not rewrite them.

Docker reference

The image is a JRE, not a published SourbyCraft image. Copy the release jar toserver.jar next to the compose file, mount it read-only, keep the world volume persistent, and pin the Java image digest for anything beyond a local test.

docker-compose.yml · reference
services:
  sourbycraft:
    image: eclipse-temurin:25-jre
    command:
      - java
      - -Xmx4G
      - -jar
      - /srv/server.jar
      - --nogui
    ports:
      - "25565:25565"
    volumes:
      - ./data:/srv
      - ./server.jar:/srv/server.jar:ro
    restart: unless-stopped

Common failures

  • Unsupported class file version: the JVM is older than Java 25. Check java -version and the service unit’s environment.
  • First boot cannot download: the launcher needs network access once. Check proxy and DNS settings; do not disable verification to get past it.
  • Checksum mismatch: the download is incomplete or altered. Re-download; do not run it.
  • Plugin timing errors: the plugin assumes a single main thread. Read Regions and the bridge notes before enabling compatibility mode.
  • Server never reaches first tick: capture the full startup log and check the Java version, memory limit, and world permissions.

Next

Read Aurora Engine for the execution model, then Operations for the commands and shutdown behavior you will need on a real server.