Upstream and attribution
SilkMC is derived from Folia and Paper. This page explains why upstream names still appear in places, and how SilkMC plans to stay close enough to upstream to keep merges manageable.
Why upstream names still appear in places
Some references remain in:
- Patch history.
- Attribution notes.
- License-related materials.
- Developer documentation about merge strategy and origin.
These references are intentional and retained for legal or maintenance reasons.
Merge strategy
- Keep region-threading internals close to upstream where possible.
- Isolate SilkMC branding and compatibility policy in small, reviewable patches.
- Prefer additive compatibility layers over broad rewrites.
binary compatibility
Upstream Folia classes still exist under their original package names so plugins compiled against Folia continue
to load. Feature-detection (rather than name-detection) is the most reliable way to identify the running server.