Threaded regions. Plugin compatibility.
SilkMC is an early-alpha, open-source Minecraft server platform forked from Folia. It preserves Folia's regional multithreading architecture and layers a compatibility-focused policy on top so that Paper, Bukkit, and Spigot plugins fail clearly instead of silently corrupting state.
At a glance
Inherited directly from Folia. Each ticking region runs on a scheduler-managed worker — no fake single main thread.
Architecture →Legacy BukkitScheduler and sync teleport calls are bridged where it is safe; unsafe patterns fail loudly.
Auto-generated config, per-plugin overrides, a /silkmc command, and structured compatibility reports.
Plugin startup paths, scheduler bridging, lifecycle timing, async-misuse diagnostics, and readable incompatibility reports.
compatibility layerNo fake global main thread. No silent cross-region writes. No ownership-check bypasses. SilkMC fails cleanly when correctness is at risk.
guardrailsProject stage
SilkMC is currently at v0.1.5-alpha on the ver/26.1.x branch, tracking upstream
Folia 26.1.2. The build toolchain is JDK 25 with Gradle and the Paperweight patch workflow.
Goals
- Preserve high-throughput regional multithreading from Folia.
- Maximize compatibility with Paper, Bukkit, and Spigot plugins.
- Keep vanilla gameplay stable — redstone, AI, chunk loading, combat, scoreboards, commands, world gen, networking.
- Prefer safe fallbacks, detailed warnings, and maintainable architecture over risky hacks.
How the docs are organized
Get the runnable paperclip jar, configure SilkMC, and understand how it behaves on first boot.
Install →The execution model, the region logic SilkMC inherits, and the compatibility policy it layers on top.
Architecture →Author guidance, recommended metadata, an evolving compatibility matrix, and operator commands.
Plugin developers →