CombatKeepInventory Velocity 是 CombatKeepInventory 在 Velocity 网络中的代理端组件。
它跨后端服务器跟踪并同步玩家战斗状态,使 Minecraft 网络能够区分合法的服务端切换与玩家在战斗中离开网络。
Velocity 实现通过战斗状态桥接器与 Bukkit/Paper 版 CombatKeepInventory 插件配合使用。
功能特性
- 代理端战斗会话跟踪
- 战斗状态同步
- 后端服务器切换检测
- 集群/网络退出检测
- 战斗登出检测
- 玩家会话跟踪
- 跨服务器战斗状态同步
- FORCE_END(强制结束)战斗状态支持
- 插件消息传递支持
- Velocity 平台检测
- Core API 集成
- 可配置的代理行为
- 命令与管理控制
网络架构
CombatKeepInventory Velocity 作为代理端组件运行。
后端服务器运行 Bukkit/Paper 版的 CombatKeepInventory。
两个组件通过 CombatKeepInventory 战斗状态桥接器进行通信。
当前协议使用以下战斗状态消息:
START(开始)
REFRESH(刷新)
END(结束)
FORCE_END(强制结束)
这允许战斗状态在合法的后端服务器转移中得以保留,同时仍能让代理识别真正离开网络的玩家。
服务器切换
玩家从一个后端服务器切换到另一个后端服务器时,不会自动被视为战斗登出。
Velocity 组件会跟踪玩家会话和服务器过渡,以便将服务器切换与实际的网络断开连接分开处理。
要求
- Velocity
- Java 21+
- 后端服务器上安装 CombatKeepInventory Bukkit/Paper
本插件专为 Velocity 网络设计,不作为 Bukkit/Spigot/Paper 插件运行。
命令
命令及其权限可根据已安装的版本进行配置。
安装
- 将 CombatKeepInventory Velocity 安装到 Velocity 的 plugins 目录中。
- 在每个应参与战斗同步的后端服务器上安装 CombatKeepInventory Bukkit。
- 配置代理和后端组件。
- 确保后端服务器通过同一个 Velocity 代理连接。
- 重启网络。
Velocity 和 Bukkit 项目分别发布,不得放置在错误的 plugins 目录中。
CombatKeepInventory Velocity is the proxy-side component of CombatKeepInventory for Velocity networks.
It tracks and synchronizes player combat state across backend servers, allowing a Minecraft network to distinguish between legitimate server switching and leaving the network while a player is in combat.
The Velocity implementation is designed to work with the Bukkit/Paper CombatKeepInventory plugin through the network combat state bridge.
Features
- Proxy-side combat session tracking
- Combat state synchronization
- Backend server switch detection
- Cluster/network exit detection
- Combat logout detection
- Player session tracking
- Cross-server combat state synchronization
- FORCE_END combat state support
- Plugin messaging support
- Velocity platform detection
- Core API integration
- Configurable proxy behavior
- Commands and administrative controls
Network architecture
CombatKeepInventory Velocity acts as the proxy-side component.
Backend servers run the Bukkit/Paper version of CombatKeepInventory.
The two components communicate through the CombatKeepInventory combat state bridge.
The current protocol uses the following combat state messages:
START
REFRESH
END
FORCE_END
This allows combat state to survive legitimate backend server transfers while still allowing the proxy to identify a player who actually leaves the network.
Server switching
A player changing from one backend server to another is not automatically treated as a combat logout.
The Velocity component tracks the player session and server transition so that server switching can be handled separately from an actual network disconnect.
Requirements
- Velocity
- Java 21+
- CombatKeepInventory Bukkit/Paper on backend servers
This plugin is intended for Velocity networks and does not run as a Bukkit/Spigot/Paper plugin.
Commands
Commands and permissions are configurable according to the installed version.
Installation
- Install CombatKeepInventory Velocity into the Velocity plugins directory.
- Install CombatKeepInventory Bukkit on each backend server that should participate in combat synchronization.
- Configure the proxy and backend components.
- Ensure the backend servers are connected through the same Velocity proxy.
- Restart the network.
The Velocity and Bukkit projects are released separately and must not be placed in the wrong plugins directory.
评论 0
登录后参与评分
还没有评论,来抢沙发吧