📋 Changelog

All notable changes to SupperBackpack will be documented in this file.

---

[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.db instead 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

1. On first startup with v1.2.0, the plugin scans for existing YAML files
2. All player data (tier, items) is migrated to backpacks.db
3. Original YAML files are moved to player_storage_db/migrated/ for backup
4. No manual intervention required!

📝 Technical Details

• New DatabaseManager.java class 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: players table (username, tier, last_used) and backpack_items table (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.yml that 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