Changelog: 09.04.2026 [Hotfix 3.1.1]

Fixed

• Fixed a bug in the /backpack remove owner command that caused an error when the backpack was not loaded in memory

For the full changelog, see 3.1.0

Changelog: 09.04.2026 [Release 3.1.0]

⚠️ Note: If you are upgrading from an older version, please update your message configurations to the MiniMessage format, as Legacy Colors are no longer supported. Failure to do so will result in your messages appearing without colors. If something doesn't work as expected, please report the error on Discord or GitHub Issues.

⚠️ 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

• Main:
  • Updated NBT-API to the latest version
  • The plugin now runs on version 26.1.1
  • Player names are now updated in the database upon joining the server
• Fixed:
  • Fixed an SQLite error related to a duplicate tier column, which could prevent the plugin from starting if the database didn't exist
  • Fixed incorrect timestamps caused by a rare bug
• Added:
  • Added an admin command to change backpack ownership: /backpack force transfer owner <backpack uuid> <player> | Permission: backpackplus.admin.force.transfer.owner
  • Added a feature to save the last viewed backpack page - when a player reopens their backpack, it will now open on the same page they previously closed (if this option is enabled: keep-player-last-backpack-page)
  • Added an option to block backpack opening when interacting with specific blocks:

  # While holding the backpack, clicking on a block will trigger the block's native interaction instead of opening the backpack
  blocked-backpack-interaction-blocks:
    - CRAFTING_TABLE
    - ENDER_CHEST
    - ENCHANTING_TABLE
    - ANVIL
    - GRINDSTONE
    - LOOM
    - SMITHING_TABLE
    - STONECUTTER
    - CARTOGRAPHY_TABLE
    - OAK_BUTTON
  

  • Added a command to delete backpacks from the database: /backpack delete <backpack uuid>. Permission: backpackplus.admin.backpack.delete
  • Added command: /backpack remove owner. Permission: backpackplus.remove.owner - used for transferring backpack ownership. After executing this command, the next person to open the backpack will become its new owner.
  • If a backpack has a pending ownership change NBT, the owner's name will no longer be displayed; instead, the default placeholder from the config will be shown.
• Changed:
  • Expanded the inventory backpack limit system:

  # Block the possibility of having more than the set number of backpacks in the inventory
  limit-backpack-per-inventory:
    # If true, the plugin will check and enforce the backpack limit for players
    enable: false
    # The default limit for players who do not have any specific permission from the list below
    default-limit: 1
    # Custom limits based on permissions.
    # If a player has multiple permissions, the highest value will be granted.
    # Format: "permission.node": limit_amount
    permissions:
      "backpack-limit-1": 1
      "backpack-limit-2": 2
      "backpack-limit-3": 3
  

  • Updated language files
  • Changed the update check provider from SpigotMC to Modrinth

---

Upgrade Steps

1. Backup the necessary files and database as described above.
2. Replace the existing plugin files with the new version.
3. Update config.yml according to the latest format.
4. Update your language file to the MiniMessage format.
5. Restart the server and verify that everything is functioning correctly.

---

Changelog: 25.02.2026 [Release 3.0.0]

⚠️ Note: If you are upgrading from an older version, please update your message configurations to the MiniMessage format, as Legacy Colors are no longer supported. Failure to do so will result in your messages appearing without colors. If something doesn't work as expected, please report the error on Discord or GitHub Issues.

⚠️ 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

• Main:

  • Spigot servers are no longer supported.
  • Paper API has been implemented instead of Spigot API.
  • Legacy Colors are no longer supported; please update them to the MiniMessage format. You can use the default files as a template.
  • All messages now support the MiniMessage format.
  • The plugin now supports versions 1.20 and newer.

• Added:

  • Added a check to verify if the server software is supported (Folia / Paper / Paper forks).
  • Added pagination for the GUI showing all players' backpacks.
  • Added the ability to set a default placeholder for <backpack_owner>:

    • backpack-placeholders-defaults: 
        backpack-owner-name: "<#1cc2f6><player>"
      

  • Added new NBT tags for backpacks:
    • Backpack Owner UUID
    • Backpack Owner Name
  • Added a template for backpack lore content (colors and formatting can now be customized):

    • # Default values for backpack placeholders
      backpack-placeholders-defaults:
        #... other
        # <amount> = amount of specific item
        # <name> = material or custom item name
        content-lore-template: "<#f9c100><amount>x <#dadada><name>"
      

  • You can now customize virtually all messages.
  • Added a custom logging system for testing purposes.
  • Added the /backpack recipes command (backpackplus.view.recipes), which displays all craftable backpacks.
  • Added a new config option to prevent opening a backpack when right-clicking a chest or similar block; the block will be opened instead. This also applies to doors and trapdoors: block-interaction-blocks-prevent-backpack-open.
  • Added support for Folia.
  • Added an option to hide tooltips for GUI elements.
  • Added the remove-inactive-backpacks option, which removes inactive backpacks after a specified number of days.
  • Added support for these plugins:
    • DeluxeCombat
    • PvPManager
  • Added an option to enable or disable the ability to use backpacks during combat (if you have one of the supported plugins installed). Option: allow-open-backpacks-in-combat: false
  • Added cannot-use-in-combat message to language files

• Removed:

  • Removed saving the backpack tier and size within the content.
  • GUI buttons will no longer be saved in the content.

• Fixed:

  • All players' backpacks are no longer loaded when the plugin starts.
  • Fixed saving backpacks during plugin shutdown (the plugin will now wait for the save to finish).
  • Saving all backpacks is now performed with a single query instead of separate queries.
  • Fixed the function for checking if a String is valid Base64; it no longer incorrectly detects materials as Base64.

• Database

  • Improved the database code.
  • Overhauled the entire database system for significantly faster performance.
  • Added a tier column for backpacks in the database (backpacks will automatically update in the database).

---

Upgrade Steps

1. Backup the necessary files and database as described above.
2. Replace the existing plugin files with the new version.
3. Update config.yml according to the latest format.
4. Update your language file to the MiniMessage format.
5. Restart the server and verify that everything is functioning correctly.

---

Changelog: 12.09.2025 [Release 2.0.1]

⚠️ Note: This version is not compatible with the old config (older than 2.0.0). Rename or delete it and restart the server to generate the default config, then update it. 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

• Fixed:
  • Fixed a bug where last_player_uuid was null, which caused the backpack to not load correctly

---

Upgrade Steps

1. Backup the necessary files and database as described above.
2. Replace the existing plugin files with the new version.
3. Update config.yml according to the latest format (refer to the provided config template for 2.0.0).
4. Restart the server and verify that everything is functioning correctly.

---

Changelog: 07.09.2025 [Release 2.0.0]

⚠️ Note: This version is not compatible with the old config. Rename or delete it and restart the server to generate the default config, then update it. 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

• Added:
  • Added limit for lore - maximum can be 256 lines (minecraft limit)
  • Added configuration option: allow-bundles-in-backpacks: "Should it be possible to place bundles in backpacks?"
  • Added more database configuration options
  • Added command for console: /backpackplus mysql pool stats
  • Added option for limit-backpack-per-inventory
  • limit-backpack-per-inventory-amount determines how many backpacks a player can have in inventory at one time
  • Added all gui names to language files now you can translate them, etc.
  • Added all BackpackPlus items to language files so you can translate them any way you like
  • Added display of last player's name in backpack preview
  • Added check for newer database backpack if you use backpack on several servers
  • Added a column to the database: is_open (It should create itself)
• Fixed:
  • Blocking backpacks from being placed into bundles now works for all bundle types
  • Fixed the show-content option, which, when set to false and the description was empty, would still add the backpack's contents to the lore
  • Fixed bug with non-existent setMaxStackSize method on version 1.20.1 if it does not exist it will not be set
  • Fixed loading of backpacks in admin panel if settings for that backpack are not found
• Updated:
  • Updated the class responsible for MySQL to be compatible with the updated dependencies.
  • Replaced the fields use-ssl and check-server-certificate with ssl-mode (Modern TLS switch: when set, overrides the legacy flags below: DISABLED | PREFERRED | REQUIRED | VERIFY_CA | VERIFY_IDENTITY)
  • Language files updated
  • Updated libraries
• Improved:
  • Rewritten the class responsible for backpack gui interactions
  • Improved several functions

---

Upgrade Steps

1. Backup the necessary files and database as described above.
2. Replace the existing plugin files with the new version.
3. Update config.yml according to the latest format (refer to the provided config template for 2.0.0).
4. Restart the server and verify that everything is functioning correctly.

---