What PlayerKits 2 works with.
| Platform | Java Edition |
|---|---|
| Loaders | Paper, Purpur, Spigot |
| Minecraft versions | 1.8.9, 1.12.2, 1.16.5, 1.18.2, 1.20.1, 1.21.1, 1.21.11, 26.1, 26.2 |
PlayerKits 2 turns a stack of items into a claimable kit on a GUI menu, so Paper and Spigot admins can gate gear behind a permission, a one-time claim, a cooldown, or an in-game price instead of writing a custom command for each rank. It runs on Bukkit-family server software from 1.8.9 through the current 26.2 release, and it makes no changes on the player's side beyond the inventory items a claimed kit hands over.
Building and editing kits
Creating a kit takes no config editing to start: hold the items you want in your inventory, run /kit create <name>, and PlayerKits 2 snapshots that inventory as the kit. From there, /kit edit <name> opens an in-game GUI for cooldowns, permissions, one-time claims, auto-equip armor and offhand slots, and claim requirements, so most day-to-day changes never touch a YAML file directly.
- Per-kit cooldowns, with a bypass permission available for staff.
- One-time claims, also with a dedicated bypass permission.
- Permission or price requirements, with price checks readable through PlaceholderAPI variables.
- Auto-equip armor and offhand items on claim.
- Separate display items for a kit's default, no-permission, on-cooldown, and already-claimed states.
Permissions and commands
Every command runs under /kit, with /playerkits and /kits registered as aliases.
- /kit — opens the kit GUI.
- /kit claim <kit> (or /kit <kit> when enabled) — claims a kit outside the GUI.
- /kit create <kit> — creates a kit from the items in your inventory.
- /kit edit <kit> — edits a kit's properties in a GUI.
- /kit give <kit> <player> — gives a kit, ignoring cooldown, permission, and requirements.
- /kit delete <kit> — deletes a kit.
- /kit reset <kit> <player|*> — resets claim data for one player or everyone.
- /kit preview <kit> [player] — previews a kit's contents without claiming it.
- /kit reload — reloads the configuration.
Three permission nodes cover admin access: playerkits.admin grants every command, playerkits.bypass.cooldown skips cooldowns on every kit, and playerkits.bypass.onetime skips the one-time claim limit on every kit. Which players can claim which individual kit is set per kit inside /kit edit, not through a fixed permission list.
Compatibility and integrations
PlayerKits 2 has no required dependencies. It installs standalone on Paper, Purpur, or Spigot, and optionally reads PlaceholderAPI variables for custom kit requirements or display text. Kit data can also move from the default flat-file storage into MySQL for setups that need the same kits shared across more than one backend server.
Questions about PlayerKits 2.
5 questions
How do I install PlayerKits 2?
Download the jar from Modrinth or SpigotMC, drop it into your server's plugins folder, and restart Paper, Purpur, or Spigot (a reload will not register it). The plugin generates its config and kit files on first launch. Hold the items for a kit and run /kit create <name>, then use /kit reload after any manual config edit.
Does PlayerKits 2 need Vault or PlaceholderAPI?
No. Modrinth lists no required dependencies, and the plugin runs standalone out of the box. PlaceholderAPI is optional, needed only if a kit's requirement or display text should read a value from it. MySQL storage is also optional, useful for sharing kit data across multiple servers instead of the default flat-file storage.
Which Minecraft version does PlayerKits 2 support?
PlayerKits 2 supports Paper, Purpur, and Spigot from 1.8.9 through the current 26.2 release, all from a single jar (build 1.23.3, published August 2026). There is no separate legacy download to track, so the same file covers both an old 1.x server and a current 26.x one.
Can players buy kits with in-game currency?
Yes, if the admin sets it up. Each kit can carry an optional price alongside, or instead of, a permission requirement, and PlaceholderAPI variables can drive other custom conditions. A kit with no price or permission set claims freely, subject only to its cooldown.
Is PlayerKits 2 safe to use?
PlayerKits 2 is open source under the MIT License, with its code published on GitHub and over 300,000 downloads recorded on Modrinth. It has no required dependencies and makes no client-side changes, since it only runs on the server. Download it from Modrinth, SpigotMC, or the linked GitHub repository, not a third-party mirror.
