Tags
Creators
Details
1.2
Compatibility
Changes
π BackpackPro v1.2 β The Stability Update
This update focuses on security, administrative control, and performance. We have completely overhauled the permission system to ensure your server economy remains balanced.
π‘οΈ Security & Permissions
- Hard-Locked Commands: Fixed an issue where players could sometimes bypass permissions. All commands now strictly follow the
plugin.ymldefaults. - Permission Hierarchy: *
backpackpro.useβ Now defaults to OP only.backpackpro.adminβ Added for administrative tasks.backpackpro.size.[1-6]β Enhanced detection for rank-based sizes.
- Default Protection: If a player has no size permissions, the plugin now safely defaults to 1 row (9 slots) instead of failing to open.
π οΈ New Features
- Admin Reload Command: Added
/bpreload(Alias:/bpr).- Reloads both
config.yml(messages/settings) anddata.yml(player data) without needing to restart the server.
- Reloads both
- Improved Inventory Listener: Optimized the title-matching logic to be more robust, preventing conflicts with other GUI-based plugins.
- Enhanced Sorting Logic: The right-click sorting trigger is now more responsive and checks permissions more accurately.
π Bug Fixes
- Fixed "Permission Leak": Resolved a bug where certain server configurations allowed non-permitted players to open backpacks.
- Shulker Safety: Reinforced the block on opening Shulker Boxes inside backpacks to prevent nested-storage exploits.
- Code Cleanup: Optimized the
BackpackManagerclass for better performance during item serialization (Base64).
π₯ How to Update
- Stop your server.
- Replace the old
BackpackPro.jarwith the new v1.2 version. - Delete/Rename your old
config.yml.Note: v1.2 introduces new message nodes and permission settings. Deleting the old file allows the plugin to generate the updated version automatically.
- Start your server.
Developed with care by Marbzy
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:Htej7lPO:PAEV60mY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Htej7lPO:PAEV60mY"
}

