Links
Tags
Creators
Details
All versions
1.6.0
Release
PerPlayerKit 1.6.0last year 354
Compatibility
Minecraft: Java Edition
1.21–1.21.6
1.20.x
1.19.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
1.6.0 Update
This update introduces a variety of new features, essential bug fixes, and quality-of-life improvements.
New Features:
- PlaceholderAPI Integration: Added support for PlaceholderAPI in the messages section of the configuration, allowing for more dynamic and personalized messages.
- Enhanced Kit Management: Implemented a display name option for the
%player%placeholder, offering greater customization. - Interactive UI/UX: Incorporated new sounds for saving kitroom items and enhanced the kit GUI with more interactive sound feedback.
- Improved Regear Shulker: Introduced new features for the regear shulker, including an option to prevent players from placing items into the regear inventory.
- Setup Guide: A new setup guide has been added to assist with initial configuration and usage.
Bug Fixes & Improvements:
- Connection Stability: Resolved a critical connection leak in
SQLStorage.javaand improved SQL resource management by implementing try-with-resources. - Visual Corrections: Fixed a visual bug where inventories were not updating correctly on repair and addressed an issue with fill items in view-only ender chests.
- Command Enhancements: The
/inspectkitcommand has been significantly improved, now allowing administrators to change player kits. The/enderchest1-9command also received a fix. - Performance & Reliability: Added a CI pipeline to improve development consistency, and implemented measures to prevent public kit load spam. Configuration options for
maximumPoolSizehave been added for both MySQL and SQLite to enhance database connection management. - Configuration & Reverts: Clarified button functionality and updated the default regear item whitelist. Reverted changes related to Hikari for SQLite and
sqlite maximumPoolSizesetting to ensure stability. - Minor Adjustments: Included a
DisabledCommandcheck toRegearCommand.javaand made various minor code and configuration updates to refine functionality.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ol7vQoT5:C1e9lDnA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ol7vQoT5:C1e9lDnA"
}

