diff options
Diffstat (limited to 'docs/src/en')
| -rw-r--r-- | docs/src/en/guide/admin/velocity.md | 35 | ||||
| -rw-r--r-- | docs/src/en/reference/permissions.md | 54 |
2 files changed, 70 insertions, 19 deletions
diff --git a/docs/src/en/guide/admin/velocity.md b/docs/src/en/guide/admin/velocity.md index 6a4e6f7..e1f9aa0 100644 --- a/docs/src/en/guide/admin/velocity.md +++ b/docs/src/en/guide/admin/velocity.md @@ -21,13 +21,8 @@ To enable Velocity integration, follow these steps: For Velocity and Paper's LunaticChat to integrate correctly, both plugin versions and protocol versions must be compatible. - Ensure that the LunaticChat versions on Velocity and Paper sides are the same. - - Generally, the same version of LunaticChat is compatible. - - Releases are made simultaneously for Velocity and Paper versions, so version numbers will not differ. - - However, compatibility may not be guaranteed when using beta or development versions. + - Compatibility may not be guaranteed when using beta or development versions. - Ensure that protocol versions match. - - LunaticChat uses protocol versions to ensure compatibility between different versions. - - Verify that the protocol versions of LunaticChat on Velocity and Paper sides match. - - Note that when protocol versions change, it is considered a **breaking change**, requiring simultaneous updates of both Velocity and Paper versions of LunaticChat. ::: danger Regarding LunaticChat versions prior to v0.7.0 @@ -37,34 +32,36 @@ They cannot be used together, so if you are using LunaticChat prior to v0.7.0, d ::: -::: tip Version Rules +## How to Check Integration Status + +To verify that Velocity integration is working properly, use the `/lcv status` command. + +The current protocol version and connection state will be displayed. + +::: warning Behavior When Versions Mismatch -LunaticChat follows these version rules: +When the version or protocol version does not match, the Velocity integration feature is disabled, but **the plugin itself continues to operate**. -- Plugin version: Exact match required - - Paper 0.7.0, Velocity 0.7.0 → ✓ PASS - - Paper 0.7.0, Velocity 0.6.0 → ✗ FAIL -- Protocol version: MAJOR.MINOR must match - - Paper 1.0.0, Velocity 1.0.1 → ✓ PASS (PATCH difference is OK) - - Paper 1.0.0, Velocity 1.1.0 → ✗ FAIL (MINOR difference) - - Paper 1.0.0, Velocity 2.0.0 → ✗ FAIL (MAJOR difference) +You can check the connection state and error details using the `/lcv status` command. To reconnect, ensure that the LunaticChat version / protocol version on Velocity and Paper sides match. ::: -## How to Check Integration Status +::: tip About Velocity Integration Timing -To verify that Velocity integration is working properly, use the `/lcv status` command. +LunaticChat connects to Velocity **when the first player joins the server** after startup. -The current protocol version and connection state will be displayed. +Therefore, if you run the `/lcv status` command immediately after server startup, the Velocity integration may not be established yet. + +::: ## Troubleshooting If you encounter issues with Velocity integration, check the following: +- **Run the `/lcv status` command to check the connection state**. If there are errors such as version mismatches, an error message will be displayed. - Ensure that the LunaticChat version / protocol version on Velocity and Paper sides are the same. - Verify that LunaticChat settings are correct. - Ensure that network connection between Velocity server and Paper servers is working properly. -- Check LunaticChat logs for error messages or warnings. ## Cross-Server Chat diff --git a/docs/src/en/reference/permissions.md b/docs/src/en/reference/permissions.md index 65825c1..4508808 100644 --- a/docs/src/en/reference/permissions.md +++ b/docs/src/en/reference/permissions.md @@ -20,6 +20,12 @@ Receives LunaticChat update notifications. [You must have `checkForUpdates` enabled](../guide/admin/configuration.md#checkforupdates) to receive notifications. +### `lunaticchat.channelbypass` + +- Default: `OP` + +Bypasses moderation features and restrictions on private channels. + ## `lunaticchat.command.*` ### `lunaticchat.command.tell` @@ -94,12 +100,54 @@ Toggles the use of the [`/lc channel switch`](commands/lc/channel.md) command. Toggles the use of the [`/lc channel status`](commands/lc/channel.md) command. +### `lunaticchat.command.lc.channel.info` + +- Default: `non OP` + +Toggles the use of the [`/lc channel info`](commands/lc/channel.md) command. + ### `lunaticchat.command.lc.channel.delete` - Default: `non OP` Toggles the use of the [`/lc channel delete`](commands/lc/channel.md) command. +### `lunaticchat.command.lc.channel.invite` + +- Default: `non OP` + +Toggles the use of the [`/lc channel invite`](commands/lc/channel.md) command. + +### `lunaticchat.command.lc.channel.kick` + +- Default: `non OP` + +Toggles the use of the [`/lc channel kick`](commands/lc/channel.md) command. + +### `lunaticchat.command.lc.channel.ban` + +- Default: `non OP` + +Toggles the use of the [`/lc channel ban`](commands/lc/channel.md) command. + +### `lunaticchat.command.lc.channel.unban` + +- Default: `non OP` + +Toggles the use of the [`/lc channel unban`](commands/lc/channel.md) command. + +### `lunaticchat.command.lc.channel.mod` + +- Default: `non OP` + +Toggles the use of the [`/lc channel mod`](commands/lc/channel.md) command. + +### `lunaticchat.command.lc.channel.ownership` + +- Default: `non OP` + +Toggles the use of the [`/lc channel ownership`](commands/lc/channel.md) command. + ### `lunaticchat.command.lc.chatmode` - Default: `non OP` @@ -112,6 +160,12 @@ Toggles the use of the [`/lc chatmode`](commands/lc/chatmode.md) command. Toggles the use of the [`/lc chatmode toggle`](commands/lc/chatmode.md) command. +### `lunaticchat.command.lcv.status` + +- Default: `OP` + +Toggles the use of the [`/lcv status`](commands/lcv/status.md) command. + ### `lunaticchat.command.jp` <Badge type="danger" text="Deprecated: Will be removed in v1.0.0" /> - Default: `non OP` |