Docs: perplayerkit.com (work in progress)
| Where | Link |
|---|---|
| Modrinth | https://modrinth.com/plugin/perplayerkit |
| SpigotMC | https://www.spigotmc.org/resources/perplayerkit.121437/ |
| Hangar | https://hangar.papermc.io/noah32/PerPlayerKit |
| GitHub releases | https://github.com/rossnoah/PerPlayerKit/releases |
| Dev builds (Jenkins) | https://jenkins.noah.dev/job/PerPlayerKit/ |
Dev builds are built from the main branch on every commit and are untested — back up your kit data before running one in production.
Join the discord for more information and support: Discord
New to PerPlayerKit? Check out our Simple Setup Guide for a step-by-step walkthrough that gets you up and running in minutes!
PerPlayerKit is open source and licensed under the terms of the GNU Affero General Public License v3. 0. Read and understand the license before using this software. Frequently Asked Questions about the GNU Licenses.
If you would like to contribute to the project you can do so by forking the repository and submitting a pull request. We prefer that improvements and contributions be merged into the main branch, rather than spread across numerous forks.
PerPlayerKit is a PaperMC plugin that allows players to make their own unique kits to PvP with. Administrators create a set of items in the "Virtual Kit Room", from which players pick their items. They can then make up to 9 kits each (configurable up to 99 with the max-kits option) which can be shared, modified, and inspected by moderators. It features a GUI for simple kit usage of the plugin. Additionally, commands can be used to quickly load kits and for moderator features. It also features protections against abusive items, limiting NBT data and enchantments to what is available in vanilla Minecraft and only allowing items that can be found in the "virtual kit room". Players can also use the plugin to create enderchest kits that will be loaded into their enderchest when they select the enderchest kit.
PerPlayerKits uses a minecraft GUI library called canvas, it can be found here. PerPlayerKits was supports version 1.19 and above.
Optionally, PerPlayerKit integrates with PlaceholderAPI for placeholders in messages and WorldGuard for region-specific rekit-on-kill kits (see the configuration documentation). Neither is required.
PerPlayerKits has a minimal configuration just requiring selecting the database type. PerPlayerKit supports MySQL/MySQL compatible (MariaDB), PostgreSQL, and SQLite databases. If you don't know what you are doing or don't have access to a database, use sqlite as the database type.
To use the plugin run the server with the plugin in the "plugins" folder, then stop the server and edit the config.yml file in the "plugins/PerPlayerKits" folder.
More configuration options are available, please refer to the configuration documentation.
Need to switch storage backends? See the Storage Migration Guide for instructions on migrating data between SQLite, MySQL, PostgreSQL, Redis, and YAML storage types.
For detailed information on commands and permissions, please refer to the command documentation.
PerPlayerKit has a simple API that allows developers to interact with the plugin. The API is NOT stable and will possibly change in the future. Please refer to the API documentation for more information.