Operate · 02

Testing

This page describes how SilkMC validates compatibility with the Paper, Bukkit, and Spigot plugin ecosystems. It is intended for contributors and server operators who want to reproduce or extend the suite.

Initial validation targets

Suggested matrix

TierPlugin packGoal
1No pluginsVerify clean SilkMC startup and vanilla gameplay regressions.
2Paper-only plugin packVerify modern plugins keep their behavior unchanged.
3Mixed Paper/Bukkit/Spigot plugin packVerify legacy plugin survivability through the compatibility layer.
4Scheduler-heavy plugin pack (lots of runTaskTimer)Verify scheduler bridging stability and overhead.
5Teleport-heavy plugin pack (warps, multiverse)Verify teleport bridging stability.

Pass criteria

Smoke test checklist

The SilkMC team runs this checklist before tagging a release.

CI smoke test

Added in v0.1.5-alpha. GitHub Actions builds SilkMC, creates the paperclip jar, boots a real server, and checks latest.log. The curated plugin pack is pinned by explicit versioned download URLs, and the workflow fails on unexpected ERROR or SEVERE log lines outside ci/smoke-test-allowlist.txt. LuckPerms remains the key regression target for the scheduler bridge and delay/period clamp path.

Reporting compatibility outcomes

Open issues using the "Plugin compatibility" template. Include:

See also: plugin reports.