Tags
Creators
Details
1.3.0
Compatibility
Changes
📋 Changelog
All notable changes to SupperBackpack will be documented in this file.
[1.3.0] - 2026-01-16
🐛 Bug Fixes
Fixed Gem Effect Levels
- Critical Fix: Level 1 gems were incorrectly giving Level 2 effects
- All ability gems now properly apply the correct effect level:
- Level I gems → Effect amplifier 0 (Level I)
- Level II gems → Effect amplifier 1 (Level II)
- Affected gems: Speed, Jump, Strength, Health, Resistance, and Haste
✨ New Features
bStats Integration
- Added bStats metrics for plugin usage tracking
📝 Technical Details
- Added
getAbilityLevel()method toCustomItems.javaandSpecialItemManager.java - Modified
BuffManager.applyBuff()to accept level parameter - Uses Gradle Shadow plugin to bundle bStats dependency
[1.2.0] - 2026-01-01
🗄️ Database Storage Migration
Major Change: Player data storage has been migrated from individual YAML files to a single SQLite database for improved performance and reliability.
What's New
- Single Database File: All player data is now stored in
backpacks.dbinstead of individual YAML files per player - Automatic Migration: Existing YAML files in
player_storage_db/are automatically migrated to the database on first startup - Better Performance: SQLite provides faster read/write operations, especially for servers with many players
- More Reliable: Reduces risk of data corruption from improper YAML formatting
Migration Process
- On first startup with v1.2.0, the plugin scans for existing YAML files
- All player data (tier, items) is migrated to
backpacks.db - Original YAML files are moved to
player_storage_db/migrated/for backup - No manual intervention required!
📝 Technical Details
- New
DatabaseManager.javaclass handles all SQLite operations - Uses Base64 encoding for ItemStack serialization (BukkitObjectOutputStream)
- Username-based storage: Players are identified by username (case-insensitive), not UUID
- Database schema:
playerstable (username, tier, last_used) andbackpack_itemstable (username, slot, item_data) - Thread-safe database operations
🐛 Bug Fixes
Fixed Upgrade Gem Crafting Recipe
- Fixed issue where Upgrade Gem Tier 3 could not be used to craft Upgrade Gem Tier 4
- Added CustomModelData identifiers (1001-1004) to upgrade gems for reliable recipe matching
- Removed duplicate recipe entries in
recipes.ymlthat could cause conflicts
🔄 Upgrade Notes
- Automatic migration: Just replace the JAR file and restart
- Backup recommended: While migration is automatic, backing up your
player_storage_db/folder is recommended - Original files preserved: Migrated YAML files are moved to
migrated/folder, not deleted
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:hBTCoGAy:rXWQXIaM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hBTCoGAy:rXWQXIaM"
}

