Threaded regions, plugin compatibility work.
SilkMC keeps Folia's regional multithreading architecture while narrowing the rough edge for Paper, Bukkit, and Spigot plugins. It is meant to make failures clearer, startup safer, and testing less mysterious.
Early alpha build. Test on a backup or staging server first.
Direct download for the runnable paperclip build.
Closer to Paper plugin expectations without pretending Folia is single-threaded.
Plugins can opt into SilkMC compatibility while Folia-aware metadata remains honored for upstream interoperability.
plugin loadingLegacy task assumptions are handled where the server can preserve correctness across region-threaded execution.
thread ownershipWhen behavior cannot be made safe, SilkMC should warn, disable, or fail loudly instead of hiding a corruption risk.
guardrailsPaper, Bukkit, and Spigot plugin startup paths; lifecycle timing; scheduler assumptions; async misuse diagnostics; and more readable incompatibility reports.
It is not a guarantee that every plugin works, and it is not production-hardened yet. Test carefully before using it for anything important.
Use the runnable paperclip jar and test plugins in layers.
Apply patches first, then build the server and paperclip package.
git clone https://github.com/tame-gg/SilkMC.git
cd SilkMC
./gradlew applyAllPatches
./gradlew build
./gradlew :silkmc-server:createPaperclipJar The plain silkmc-server jar is not meant to be launched standalone.
java -Xms4G -Xmx4G -jar silkmc-server/build/libs/silkmc-paperclip-26.1.2.local-SNAPSHOT.jar nogui Add plugins gradually, keep logs from each run, and test on a backup or staging world while the alpha settles.