CombatKeepInventory Velocity

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

1. Install CombatKeepInventory Velocity into the Velocity plugins directory.
2. Install CombatKeepInventory Bukkit on each backend server that should participate in combat synchronization.
3. Configure the proxy and backend components.
4. Ensure the backend servers are connected through the same Velocity proxy.
5. Restart the network.

The Velocity and Bukkit projects are released separately and must not be placed in the wrong plugins directory.