feature key in config.yml and can be toggled independently — turn on automatic rekitting for a PvP server, add full-heal-on-kit-load for a casual experience, or strip all potion effects on respawn for a competitive environment, all without touching any other part of the plugin.
Full Configuration Block
config.yml
Kit Loading
These flags fire whenever a player loads a kit or enderchest. Use them to standardise the player’s state at the moment gear is applied.Automation
These flags control when PerPlayerKit automatically re-applies a player’s kit without requiring a manual command.rekit-on-respawn
Set to true (the default) to have PerPlayerKit automatically load the player’s last-used kit the moment they respawn after death. This is the primary automation flag for PvP servers — players return to the action fully geared without any extra steps.
rekit-on-respawn-delay is measured in ticks, not seconds. There are 20 ticks per second, so a value of 40 equals a 2-second delay. Use a non-zero delay if another plugin (such as a spawn-protection or spawn-items plugin) also gives items on respawn and the two systems conflict.config.yml
rekit-on-kill
When enabled, the player who lands the killing blow automatically reloads their last-used kit. The simple boolean form enables it in every world:
config.yml
Advanced World Filtering
For more control, replace the boolean with the expanded object form to restrict or exclude specific worlds:config.yml
1
Check the whitelist
If
world-whitelist contains one or more world names, rekit-on-kill only activates in those worlds. The blacklist is ignored entirely.2
Check the blacklist
If
world-whitelist is empty but world-blacklist has entries, rekit-on-kill activates everywhere except the listed worlds.3
Allow all worlds
If both lists are empty, rekit-on-kill activates in every world.
config.yml
config.yml
If your existing config uses the old boolean form (
rekit-on-kill: true), it will continue to work after a plugin update. PerPlayerKit will automatically add the new keys with default values — no manual migration is required.