Autopickup

To view the full change log, please visit Autopickup Changelog

This update represents a major structural shift in how AutoPickup handles your data. We’ve moved away from flat-file storage to a robust database system to ensure better performance and reliability.

🚀 New Features & Improvements

• Database Integration: Added full support for MySQL and SQLite. Your preferences are now stored more securely and retrieved faster.
• Enhanced Configuration: The config.yml has been redesigned with a dedicated database section.
• Self-Healing Configs: The new ConfigValidator now automatically repairs missing or broken configuration nodes on the fly.
• Performance Optimization: Refactored the PlayerDataManager and simplified driver loading for a smaller memory footprint.
• Logging Upgrade: Switched to SLF4J for cleaner, more professional console logging and troubleshooting.
• Updated Analytics: Integrated the latest HStats to help us better understand plugin usage and performance.

🛠️ Technical Changes

• Version Bump: Moved to version 2026.4.3.
• Data Migration: Please note that data.yml is no longer used. Data is now handled via the configured database provider.
• Refactored Commands: Internal command logic has been rewritten for better responsiveness.
• Migration logs: https://mclo.gs/c1ReQKR

Spark Usage

• Autopickup now only uses 0.26% of the thread. While we aim to keep improving this, it is a big drop from what it was. If you run into any issues, please join the BusyBee Discord and share your spark reports with us.

Standard Disclaimer: As this update changes how data is saved, we recommend backing up your existing configuration before updating.