summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSho Sakuma <me@m1sk9.dev>2026-08-05 19:46:16 +0900
committerSho Sakuma <me@m1sk9.dev>2026-08-05 19:46:16 +0900
commit639173db48d037ffa5c084d089e5fc7d85d71d80 (patch)
tree286e9a92e04bfa3f7e79fe97ce1a2046c547595b
parentaf776eac4fd971483397f40e8c8452df485892e0 (diff)
downloadLunaticChat-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>
-rw-r--r--website/src/docs/developers/resource.md4
-rw-r--r--website/src/docs/features/direct-message.md2
-rw-r--r--website/src/docs/features/velocity.md2
-rw-r--r--website/src/ja/docs/developers/resource.md4
-rw-r--r--website/src/ja/docs/features/direct-message.md2
-rw-r--r--website/src/ja/docs/features/velocity.md2
6 files changed, 8 insertions, 8 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.
diff --git a/website/src/docs/features/direct-message.md b/website/src/docs/features/direct-message.md
index ec0f24e..e799985 100644
--- a/website/src/docs/features/direct-message.md
+++ b/website/src/docs/features/direct-message.md
@@ -30,7 +30,7 @@ Replies to the last player who sent you a message. If there is no such player, t
To use quick reply, `features.quickReplies.enabled` must be `true` (default) in `config.yml`.
-## Cross-Server Direct Messages <Badge type="tip" text="v1.3.0~" />
+## Cross-Server Direct Messages <Badge type="tip" text="Paper v1.3.0~ / Velocity v1.2.0~" />
> [!NOTE]
>
diff --git a/website/src/docs/features/velocity.md b/website/src/docs/features/velocity.md
index 7842a24..f9d3814 100644
--- a/website/src/docs/features/velocity.md
+++ b/website/src/docs/features/velocity.md
@@ -53,7 +53,7 @@ Each message is assigned a unique ID, and a cache prevents the same message from
Entries expire 60 seconds after they are recorded. If the cache is still over its configured size after expired entries are cleared, the oldest remaining entries are dropped.
-## Cross-Server Direct Messages <Badge type="tip" text="v1.3.0~" />
+## Cross-Server Direct Messages <Badge type="tip" text="Paper v1.3.0~ / Velocity v1.2.0~" />
Setting `crossServerDirectMessage` to `true` lets players exchange direct messages with players on other servers connected to the same proxy.
diff --git a/website/src/ja/docs/developers/resource.md b/website/src/ja/docs/developers/resource.md
index b06864a..0eea858 100644
--- a/website/src/ja/docs/developers/resource.md
+++ b/website/src/ja/docs/developers/resource.md
@@ -20,8 +20,8 @@ Gradle マルチモジュール構成で,engine を共有しつつ Paper / Vel
```properties
# gradle.properties
-paperVersion=1.2.2
-velocityVersion=1.1.0
+paperVersion=1.3.0
+velocityVersion=1.2.0
```
Paper と Velocity は別々のバージョン番号を持ち,独立にリリースできます.**互換性を数値バージョンではなく engine 共有の [`ProtocolVersion`](/ja/docs/developers/engine#バージョニング戦略-protocolversion) で保証している**ため,更新頻度の異なる 2 プラットフォームをそれぞれのペースでバンプ・公開できるからです.ワイヤ形式は JSON + `ignoreUnknownKeys` で前方互換,プロトコルの MAJOR 一致 + MINOR 範囲チェックで後方互換をコントロールします.
diff --git a/website/src/ja/docs/features/direct-message.md b/website/src/ja/docs/features/direct-message.md
index 736a257..400d1d6 100644
--- a/website/src/ja/docs/features/direct-message.md
+++ b/website/src/ja/docs/features/direct-message.md
@@ -30,7 +30,7 @@ layout: doc
クイック返信を利用するには `config.yml` で `features.quickReplies.enabled` が `true` (デフォルト) である必要があります.
-## クロスサーバーダイレクトメッセージ <Badge type="tip" text="v1.3.0~" />
+## クロスサーバーダイレクトメッセージ <Badge type="tip" text="Paper v1.3.0~ / Velocity v1.2.0~" />
> [!NOTE]
>
diff --git a/website/src/ja/docs/features/velocity.md b/website/src/ja/docs/features/velocity.md
index 9020ea1..70c34fd 100644
--- a/website/src/ja/docs/features/velocity.md
+++ b/website/src/ja/docs/features/velocity.md
@@ -53,7 +53,7 @@ features:
エントリは記録から 60 秒で期限切れになります.期限切れエントリを削除してもなお設定サイズを超えている場合は,残りのうち古いものから削除されます.
-## クロスサーバーダイレクトメッセージ <Badge type="tip" text="v1.3.0~" />
+## クロスサーバーダイレクトメッセージ <Badge type="tip" text="Paper v1.3.0~ / Velocity v1.2.0~" />
`crossServerDirectMessage` を `true` にすると,同プロキシ内で接続しているサーバーのプレイヤー同士でメッセージのやり取りができるようになります.