docs: standardize the plugin build baseline on Paper API - #26
Merged
Merged
Conversation
This was referenced Sep 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TFMC runs Paper, but the platform matrix and several build guides still specify Spigot API. Standardize the baseline on
io.papermc.paper:paper-api:1.21.10-R0.1-SNAPSHOTwith provided scope and the PaperMC Maven repository. Update the affected project guides and include Archaeo in the matrix.Validation: 5 documentation checker tests, 679 local links and anchors, and strict CoreProtect MkDocs build passed. The 29 companion plugin migrations passed clean Maven verification with 2,647 tests and no bundled server API classes.
Companion source PRs (merge these before the documentation):