diff options
| author | Sho Sakuma <me@m1sk9.dev> | 2026-08-05 04:51:22 +0900 |
|---|---|---|
| committer | Sho Sakuma <me@m1sk9.dev> | 2026-08-05 04:51:22 +0900 |
| commit | 7e791eaef4e838f590585ab4dc3a3c0e6e7f0972 (patch) | |
| tree | ed5510c8737c13728dbfcf5b360b385fd2652f6b /README.md | |
| parent | 89c8e68341b0ff9cb3c69f0ff6e4c34bbec43ae9 (diff) | |
| download | LunaticChat-7e791eaef4e838f590585ab4dc3a3c0e6e7f0972.tar.gz LunaticChat-7e791eaef4e838f590585ab4dc3a3c0e6e7f0972.tar.bz2 LunaticChat-7e791eaef4e838f590585ab4dc3a3c0e6e7f0972.zip | |
docs: correct the cross-server DM server name and two related claims
The `@<server>` argument resolves against the server names registered in
`velocity.toml`, not the `features.velocityIntegration.serverName` of the
destination: PresenceTracker publishes `serverInfo.name` and
CrossServerDirectMessageRelay matches the target against the same, so the
previous text had it exactly backwards. Following it on a proxy where the two
names differ produces SERVER_NOT_FOUND every time, and points the reader at the
wrong file to fix. `serverName` still matters, for `{server}` and for
recognising local players, so what it does is stated instead.
Also corrects two claims made while widening these pages:
- `/lcv status` reports only this server's protocol version, not both sides'.
The Velocity bug template leaned on it as its most important field, so a
reporter would have pasted output that cannot answer the compatibility
question. It now also says to run it after a player has joined, since the
handshake waits for one - the same caveat the README install steps needed.
- Spies see pre-conversion text for direct messages only. Channel messages are
converted before the handler runs, so spies get the same formatted string the
members do.
Co-Authored-By: Claude <noreply@anthropic.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -56,7 +56,7 @@ Paper and Folia use `LunaticChat-<version>.jar`; Velocity proxies use `LunaticCh 1. Place `LunaticChat-<version>-velocity.jar` into the Velocity `plugins/` directory 2. Start (or restart) the proxy 3. Set `features.velocityIntegration.enabled` to `true` in the `config.yml` of every backend server -4. Restart the backend servers, then check the connection with `/lcv status` +4. Restart the backend servers, then check the connection with `/lcv status` — the handshake is sent once a player joins, so an empty server reports `DISCONNECTED` For more detail, see [Getting Started](https://lc.m1sk9.dev/docs/getting-started). |