summaryrefslogtreecommitdiff
path: root/website/src/docs/developers/resource.md
diff options
context:
space:
mode:
authorSho Sakuma <me@m1sk9.dev>2026-08-02 17:43:50 +0900
committerGitHub <noreply@github.com>2026-08-02 17:43:50 +0900
commit45c29405be5169e088023aa01cde50467f3eabed (patch)
tree7a5ef472546694d939535a9f1d6d1fb4cbc15f5e /website/src/docs/developers/resource.md
parentc2575cc3089819e3cd877c743b78f11bc9131e79 (diff)
downloadLunaticChat-45c29405be5169e088023aa01cde50467f3eabed.tar.gz
LunaticChat-45c29405be5169e088023aa01cde50467f3eabed.tar.bz2
LunaticChat-45c29405be5169e088023aa01cde50467f3eabed.zip
feat: support Paper 26.2 (Minecraft 26.2)
Paper 26.2 bundles Adventure 5.2.0, a major bump from the 4.26.1 shipped by 26.1. Adventure 5 makes ClickEvent generic, so the raw type in CommandContext.replyWithEvent no longer compiled. Auditing the rest of the Adventure 5 removals found no other affected usage. api-version is raised to 26.2, dropping 26.1 support: the two Adventure majors are not binary compatible, so claiming 26.1 compatibility would be a lie. Also fixes two problems found while verifying on a real server: the Velocity healthcheck invoked mc-health, which does not exist in the mc-proxy image, so the container had never once passed its check; and the debug environments pinned no build at all, which meant the proxy came up as 4.1.0-SNAPSHOT while the plugin is compiled against velocity-api 3.5.1. Server versions are now derived by x from the Gradle coordinates so they cannot drift from what the plugin targets.
Diffstat (limited to 'website/src/docs/developers/resource.md')
-rw-r--r--website/src/docs/developers/resource.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/website/src/docs/developers/resource.md b/website/src/docs/developers/resource.md
index 2859480..ccc9eec 100644
--- a/website/src/docs/developers/resource.md
+++ b/website/src/docs/developers/resource.md
@@ -38,7 +38,7 @@ The release target switches based on the tag pattern.
- Common flow: `validate` (check for a duplicate existing release) → `build` (mise + Gradle setup, `shadowJar`) → `release` (`gh release create --draft` + publish to Modrinth)
- The per-platform workflows (paper / velocity) differ from `release.yaml` in requiring a strict match between the tag and `gradle.properties`
-- Modrinth game-versions are Paper=`26.1.x` (loaders: paper, folia) and Velocity=`1.21.x` + `26.1.x` (loader: velocity)
+- Modrinth game-versions are Paper=`26.2.x` (loaders: paper, folia) and Velocity=`1.21.x` + `26.1.x` + `26.2.x` (loader: velocity)
## CI
@@ -53,6 +53,7 @@ The release target switches based on the tag pattern.
- `mise.toml` — bun / java zulu-25 (consistent with `JVM_25`)
- `x` — a bash debug-server script. `./x <action> <platform> [--stable]` for start/stop/log/clean/rcon/help. Without `--stable` it builds nightly. With `velocity` it brings up **1 Velocity + 2 Paper** so you can test cross-server chat relay for real
- `docker/` — `compose.yaml` for three environments: paper / velocity / folia (`itzg/minecraft-server:java25`, etc.). velocity.toml enables plugin messaging with `bungee-plugin-message-channel=true`
+- Server versions are derived by `x` from the `paper-api` / `velocity-api` coordinates in `build.gradle.kts` and passed to Compose as `PAPER_MC_VERSION` / `PAPER_BUILD` / `VELOCITY_VERSION`, so the debug environments always run the build the plugin is compiled against. Invoking `docker compose` directly fails with a message telling you to go through `./x`. Only Folia's build number is pinned by hand, since it is numbered separately from Paper
## Related