Skip to content

Kits

Kits are named item bundles stored by EssentialsLite. The kit feature is controlled by kit.enabled. Players claim a kit with /kit; administrators create, edit, and delete kits with the kit management commands.

Commands

Command Alias Usage Purpose
/kit kit /kit <name> Give a named kit to a player.
/kitpreview previewkit /kitpreview <kit> Preview a kit without claiming it. Requires essentials.kit.preview.
/createkit createkit /createkit <name> Create a kit from the creator’s current kit data.
/editkit editkit /editkit <name> Edit an existing kit.
/deletekit delkit, deletekit /deletekit <name> Delete an existing kit.
/kiteditor kitedit /kiteditor Open kit management when permitted.

The e-prefixed command labels in the command reference (/ekit, /ekitpreview, /ecreatekit, /eeditkit, and /edeletekit) are the command registrations; the user-facing aliases are shown above.

Kit Data

A kit is identified by its name and contains its serialized item contents. The editor also uses the kit’s configured metadata fields, including its permission and cooldown where those fields are present in the installed configuration. Preserve the field names and item serialization produced by the plugin when moving kit data between servers; do not hand-edit item payloads unless the installed version documents that format.

Kit-related placeholders are not registered by the EssentialsLite PlaceholderAPI expansion. Use the normal expansion values documented in Placeholders, such as %essentials_rank% or %essentials_balance%, in surrounding menus or messages only when the consuming plugin supports them.

Permissions

The source-confirmed kit permission is essentials.kit.preview, enabled by default, for /kitpreview. The command reference does not assign additional command permissions for /kit, /createkit, /editkit, or /deletekit; configure access through the command or permission setup supplied by the installed build rather than assuming an EssentialsX permission name.

Configuration And Examples

Enable kits in the plugin configuration:

kit:
  enabled: true

Typical workflow:

/createkit starter
/kitpreview starter
/kit starter
/editkit starter
/deletekit starter

The exact editor fields and item serialization are version-owned data. Keep a backup before deleting or editing a production kit.

Edge Cases And Interactions

  • Kit commands are unavailable while kit.enabled is false.
  • Previewing does not claim the kit; claiming is performed with /kit.
  • Kit names must be passed as the command argument shown above. Use the server’s command help for the authoritative list of currently stored kits.
  • A kit’s configured permission and cooldown, when set, can restrict claiming independently of the global feature switch.
  • Kit contents and metadata are persisted by the plugin. Restart or reload only according to the installed build’s reload behavior; a restart is the safe choice after structural configuration changes.