Configuration

The current configuration layout, the upcoming Build 49 rename, and the rules for editing files without losing a working server.

SourbyCraft’s configuration is split between the server/world layer and the Aurora runtime. The most important fact about the current release is that Build 48.4 keeps the older layout: Build 49 renames files and changes formats, but that migration is not active in 48.4.

Build 48.4 layout

sourbycraft_config/	Global SourbyCraft configuration. The global file is TOML on 48.4.
Aurora config	Aurora topology and scheduling settings. Build 49 changes where the keys live; the keys themselves are preserved.
config/	Server and world configuration. Build 48.4 retains the legacy canvas-* YAML names.
server.properties	Standard Minecraft server settings such as port and online mode.
mods/	ML1 SourbyMods and their per-mod data directories.
plugins/	Paper-compatible plugins.
logs/	Runtime logs, including stall records when enabled.

first boot · create a working tree

mkdir -p sourbycraft-server
cd sourbycraft-server
java -Xms4G -Xmx4G -jar ../SourbyCraft-26.2-REL.jar --nogui

The first boot creates the files. Edit them after the server has stopped, not while a region is ticking. A configuration file is not a live API unless the release notes explicitly say the key is reloadable.

Build 49 migration

Build 49 introduces typed configuration and renames the inherited Canvas files. This is a planned layout change, not a claim that 48.4 already reads it.

Build 48.4	Build 49
sourbycraft_config/sourbycraft_global_config.toml	sourbycraft_config/sourbycraft_global_config.yml
config/canvas-server.yml	config/aurora-server.yml
config/canvas-worlds.yml	config/aurora-worlds.yml
per-world settings	config/worlds.yml
per-plugin settings	config/plugins.yml

Do not pre-migrate 48.4Copying a Build 49 directory tree onto 48.4 is not a supported migration. Wait for the release that implements it, read its migration notes, and keep a backup of the old directory.

Diagnostics

Build 48.4 reports an unreadable configuration file with the file name, line, snippet, and parser message. It does not rewrite the file. This is deliberate: a parser error is an operator decision, not an invitation for the runtime to guess.

The BRIDGE_IO lane also stays quiet during shutdown. A stopped lane reports that it is stopping, keeps its per-plugin rate limit, and does not emit a stack trace for every skipped task.

Editing rules

Stop the server before structural edits (worlds, regions, storage, compatibility mode).
Back up the entire server directory before a runtime or layout change.
Change one boundary at a time; a region change plus a plugin change is not a controlled experiment.
Do not copy secrets into a world template, screenshot, or public repository.
Read the validation output. A silent default is not a successful configuration.

JVM and deployment

jvm · conservative example

# Keep the runtime on Java 25 and give the heap a fixed ceiling.
java -Xms4G -Xmx4G -jar SourbyCraft-26.2-REL.jar --nogui

# Do not tune the heap by guessing. Observe first:
# /mspt, /perf, /sys, and the host's memory pressure.

A fixed heap ceiling makes memory pressure visible. Size it to the host, not to a screenshot of someone else’s server. Use the metrics runtime to observe before changing flags. The release does not publish a recommended player count or a benchmark.

Continue

Operations covers commands and shutdown;Install covers the first boot and layout boundaries.