diff options
| author | Sho Sakuma <me@m1sk9.dev> | 2026-08-05 19:46:16 +0900 |
|---|---|---|
| committer | Sho Sakuma <me@m1sk9.dev> | 2026-08-05 19:46:16 +0900 |
| commit | 639173db48d037ffa5c084d089e5fc7d85d71d80 (patch) | |
| tree | 286e9a92e04bfa3f7e79fe97ce1a2046c547595b /website/src/docs/developers/resource.md | |
| parent | af776eac4fd971483397f40e8c8452df485892e0 (diff) | |
| download | LunaticChat-639173db48d037ffa5c084d089e5fc7d85d71d80.tar.gz LunaticChat-639173db48d037ffa5c084d089e5fc7d85d71d80.tar.bz2 LunaticChat-639173db48d037ffa5c084d089e5fc7d85d71d80.zip | |
docs: name both plugin versions for cross-server direct messages
The badge read `v1.3.0~`, pointing at a Velocity release that does not exist.
The feature needs both halves, and the Velocity half first shipped as 1.2.0
inside the unified v1.3.0 release, so a reader hunting for Velocity v1.3.0 finds
nothing and cannot tell which proxy build carries the relay.
Also refreshes the gradle.properties example, which still showed the versions
current when it was written.
Co-Authored-By: Claude <noreply@anthropic.com>
Diffstat (limited to 'website/src/docs/developers/resource.md')
| -rw-r--r-- | website/src/docs/developers/resource.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/website/src/docs/developers/resource.md b/website/src/docs/developers/resource.md index 1526cf7..543365d 100644 --- a/website/src/docs/developers/resource.md +++ b/website/src/docs/developers/resource.md @@ -20,8 +20,8 @@ Both platforms' `processResources` compute `version` / `gitCommitHash` / `channe ```properties # gradle.properties -paperVersion=1.2.2 -velocityVersion=1.1.0 +paperVersion=1.3.0 +velocityVersion=1.2.0 ``` Paper and Velocity carry separate version numbers and can be released independently. That's because **compatibility is guaranteed by the engine-shared [`ProtocolVersion`](/docs/developers/engine#versioning-strategy-protocolversion) rather than the numeric version**, so the two platforms — which change at different rates — can be bumped and published at their own pace. The wire format is forward-compatible via JSON + `ignoreUnknownKeys`, and backward compatibility is controlled by matching MAJOR + a MINOR-range check on the protocol. |