Changelog: 21.01.2025 [Beta 1.5.0]

Important Notes

⚠️ Note: This version introduces significant changes that may not be compatible with previous versions unless config.yml is updated.
If something doesn't work as it should, report the error on Discord.

⚠️ Warning: Before proceeding with this update:

1. Backup the BackpackPlus folder to avoid losing custom configurations or data.
2. If you are using a MySQL database, ensure it is backed up to prevent any potential data loss.

Key Changes

Configuration Overhaul

• Major updates to config.yml. Refer to the updated documentation for details on the required changes.
• Added new configuration options to enhance flexibility and control.

Database Enhancements

• Optimized database queries for better performance.
• Introduced support for additional database configurations.
• Improved compatibility with MySQL and SQLite.

Added Features

• Error Message: Displayed if a backpack fails to load from the database (or does not exist).
• Backpacks After Death:
  • Saving of backpacks in inventory after a player's death.
  • To enable, set keep-backpacks-after-death to true.
  • Configurable permissions for this feature (backpackplus.keep.backpacks by default).
• Per-Backpack Material Customization.
• Cache System: Improved performance through caching.
• Filtered Backpacks:
  • Ability to set a backpack type to "filtered," allowing only specified items to be stored.
• Command for Settings:
  • /backpackplus settings <tier> to change basic backpack settings.
• Item Movement Sounds:
  • Sounds when moving items in a backpack.
  • To enable, set play-song-when-item-moved-in-backpack to true.
• Additional MySQL Options: Related to HikariCP settings.
• Backpack Descriptions: Ability to set descriptions in the configuration.
• Content Display Option: Option to disable displaying the contents of backpacks.

Upgrade Steps

1. Backup Files: Follow the instructions in the "Important Notes" section above.
2. Replace Plugin Files: Replace the existing plugin files with the new version.
3. Update config.yml: Update your configuration file to the latest format using the provided config template.
4. Restart the Server: Restart your server and verify that everything is functioning correctly.