Bukkit

v2.28.1 for MC 26.3, 26.2, 26.1.2, 1.21.11, 1.21.10, 1.21.8, 1.21.7, 1.21.6, 1.21.5

I only list the primary changes here. For information on API changes, internal changes, and changes to the language files, you can find the complete changelog on Github: https://github.com/Shopkeepers/Shopkeepers/blob/master/CHANGELOG.md

• Permission: The shopkeeper.* permission was missing some permissions.
  • shopkeeper.notify.trades
  • shopkeeper.setcurrency
  • shopkeeper.teleport
  • shopkeeper.teleport.others
  • shopkeeper.settradedcommand
  • shopkeeper.snapshot
  • shopkeeper.edit-villagers
  • shopkeeper.edit-wandering-traders
  • shopkeeper.create
  • shopkeeper.hanging-sign
• Fix: An item duplication issue with player shops introduced in v2.28.0, caused by not properly resetting the trading state on failed trade attempts.
  • Also added a safeguard that aborts subsequent trade attempts if the previous trade was not properly ended.
• Fix: An item duplication issue with player shops introduced in v2.28.0 if multiple shop containers share the same inventory, e.g. the two chests of a double chest.
• Fix: The container list migration failed for shopkeepers with snapshots, because the snapshot data does not contain the shopkeeper's world.
• Fix: The container list migration did not remove the legacy container data (chestx, chesty, chestz).
• Fix: A currency item duplication issue in player shops when the shop owner edits the offers while another player is currently trading.
  • Trades are now aborted if the trading recipe price no longer matches the price of the corresponding offer.
  • We also immediately close any open trading views now when the trade offers have been edited, so trading players don't see outdated trades.
• Fix: An item duplication issue with the shop creation item and the naming item, caused by removing used items one tick later.
• Fix: Hiring non-shopkeeper villagers only charged a part of the costs if the hire items in the player's hand did not cover the full costs.
• Fix: Shopkeeper mobs could drop items and experience if they were killed directly, e.g. by other plugins. For example, a fox shopkeeper would always drop the item in its mouth. We now clear the drops of dying shopkeeper entities.
• Fix: The trades were not updated (e.g. their out-of-stock visualization) when a shift-click trade was aborted, for example due to insufficient shop container storage space.
• Debug: Add debug command /shopkeeper testKill, which kills the targeted entity by setting its health to zero. Unlike the vanilla kill command, this bypasses damage events and can be used to test the death behavior of shopkeeper entities.
• Assumptions:
  • Remove the no longer relevant sections about our SKUnmodifiableItemStack: The implementation has changed in v2.22.0.
  • Add section regarding Inventory#equals.

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation.

Thanks!

v2.28.0 for MC 26.3, 26.2, 26.1.2, 1.21.11, 1.21.10, 1.21.8, 1.21.7, 1.21.6, 1.21.5

I only list the primary changes here. For information on API changes, internal changes, and changes to the language files, you can find the complete changelog on Github: https://github.com/Shopkeepers/Shopkeepers/blob/master/CHANGELOG.md

• Update for MC 26.3.
  • Add poplar sign and hanging sign shops.
• Add support for multiple shop containers: Shop owners can now link additional containers to their player shops.
  • Config:
    • Add max-containers-per-player-shop (default: 9). Set it to 1 to keep the previous single-container behavior.
    • Add add-container-item (default: minecraft:lime_stained_glass_pane) for the add-container button.
    • Config migration 12: Rename enable-container-option-on-player-shop to enable-player-shop-open-container. It only controls now whether players can remotely open a container's inventory from the shop editor. The container information itself is always shown.
  • Editor: If max-containers-per-player-shop is greater than 1, the container button inside the editor allows shop owners to view and edit the linked shop containers.
    • Click the green glass pane item and then a nearby container to add it as an additional shop container. The usual checks apply (supported container, not already used by another shop, within max-container-distance, etc.).
    • Left/Right-click a container to cycle through the different container types.
    • If enabled, shift-right-click a container to remotely open it and inspect its content.
    • Shift-left-click a container to remove it after additional confirmation.
  • Available container types:
    • Stock: The shop retrieves trade result items from this container. Trades show as "out-of-stock" if the required result items cannot be found across the stock containers.
    • Earnings: The shop stores received items in this container. The shop prefers to store items in earnings containers that already contain the respective item.
    • Stock and Earnings: The container stores both stock and earnings (default).
  • If max-containers-per-player-shop is 1, the container editor button behaves similar to before, but includes some additional information now. The single container (and any other previously added containers) automatically act as Stock and Earnings.
  • The container information includes the coordinates, whether the container is a double chest, whether it is missing (i.e. no longer exists in the world), and, if support for multiple containers is enabled, its container type.
  • delete-shopkeeper-on-break-container only takes effect when the last shop container is broken. Broken containers remain in the shop's list of containers and show as "missing".
  • When moving a player shopkeeper, all of its containers must remain within the configured max-container-distance.
• Add player shop expiration: Player shops can now be configured to expire after a certain duration.
  • Config:
    • Add setting player-shop-expiration-days (default: 0, disabled): If greater than 0, fully owned player shops (i.e. those that were not hired) expire and get deleted this many days after their current owner acquired them (i.e. after creation or transfer).
    • Add setting hired-player-shop-expiration-days (default: 0, disabled): If greater than 0, hired player shops expire and revert back to their for-hire state this many days after they were hired.
      • Note: Since we previously did not remember the previous hiring cost item once a shop was hired, this only applies to shopkeepers that are set for hire after this update. Existing previously hired player shops behave like fully owned player shops.
      • Expiration has no effect on shops that are currently already waiting to be hired.
      • Hiring a shop resets its expiration, even if it is hired again by its current owner, e.g. after it expired and reverted back to its for-hire state.
    • Add setting notify-shop-members-about-expiration (default: true): Controls whether shop owners and members are notified when their shops are about to expire.
      • If enabled, we notify players roughly 7 days, 3 days, 1 day, 12 hours, 1 hour and 10 minutes before their shop expires (configurable via player-shop-expiration-notification-thresholds), so they have a chance to clear their shop containers in time.
      • We remember when we last notified each player, so we avoid notifying again for the same shop and notification threshold.
      • Regardless of this setting, we always inform players about the expiration duration when they create or acquire a shop, and when a shop just expired and they happen to be online currently. However, we do not notify about shops that expired while they were offline.
    • Add setting player-shop-expiration-notification-thresholds (default: 10080,4320,1440,720,60,10): A comma-separated list of the notification thresholds in minutes before expiration at which shop members are reminded.
      • The default corresponds to 7 days, 3 days, 1 day, 12 hours, 1 hour, and 10 minutes before expiration.
      • Note: The expiration duration and notification thresholds are only rough estimates. For performance reasons, the plugin only checks for expirations and pending notifications every few minutes. Thresholds below this check interval may therefore not be reached before the shop expires.
  • Expiration is checked roughly every 5 minutes, starting 5 minutes after plugin startup.
    • Deleting an expired shop automatically unlocks its containers.
    • All expirations are logged to the server log.
  • Command: The /shopkeeper list output indicates when player shops will expire.
  • Command: Add /shopkeeper expiration [player] (alias /shopkeeper expiry) to manually list up to the next 8 shops of a player that are about to expire.
    • Permission: Without the optional player argument, this lists your own expiring shops (permission shopkeeper.expiration.own, default: true).
    • Permission: The player can be specified by name or uuid, which also accounts for offline shop members (permission shopkeeper.expiration.others, default: op).
    • This command can also be used from the console, in which case the player argument is required.
    • Note: Since the expiration duration is only an estimate, some of the listed shops may already have reached their expiration time, but not have been expired yet.
  • Metrics: Add bStats metrics player-shop-expiration-days and hired-player-shop-expiration-days.
• Changes to the hiring of player shops:
  • Previously, hiring a shopkeeper fully transferred the ownership, including the ability of the new owner to delete the shopkeeper. Admins trying to use this feature to manage a controlled market area on their server had to manually monitor for stale market booths and set up new hireable shopkeepers over time. Now, owners of hired shopkeepers are more restricted in what they can do. And in combination with the new shop expiration feature (see setting hired-player-shop-expiration-days), it is now possible to set up temporarily hired shops that automatically revert back to their for-hire state once they expire.
  • Change: Hired player shops can no longer be deleted by their shop members. Instead, the "delete" button in the editor reverts the shop to the for-hire state.
    • This also applies to admins, so that they do not unknowingly observe a behavior that differs from what other players get, and to also allow them to revert the shop to the for-hire state via the editor. Players with the shopkeeper.setforhire permission additionally receive a hint that they can use the new /shopkeeper setNotForHire command first in order to then fully delete the shop afterwards.
  • Command: /shopkeeper remove and /shopkeeper removeAll only deletes hired shopkeepers if the command executor has the shopkeeper.bypass permission.
  • Change: Members of a hired player shop can access the shop containers, but are otherwise affected by the same restrictions as other players. I.e. they cannot break or build near the containers of the hired shop. Players with the shopkeeper.bypass permission are exempt from these restrictions, as before.
  • Change: Hired player shops can no longer be moved via the editor, except by players with the shopkeeper.setforhire permission.
  • Change: The containers of hired player shops can no longer be added or removed via the editor, except by players with the shopkeeper.setforhire permission.
  • Change: Hiring a player shop clears its previous trade offers, unless the current owner re-hires the shop.
  • Change: Shops that are currently for hire no longer count towards the max-shops-per-player limit (and the shopkeeper.maxshops.<count> permissions) of the current/previous owner. Without this change, players would not be able to re-hire their expired shopkeepers, or create or hire other shopkeepers after their previously hired shopkeeper(s) expired.
  • Manual migration: Setting shops for hire requires the shopkeeper.setforhire permission, which is only granted to admins by default. If you assigned this permission to normal players in the past, it is recommended that you remove this permission from them again, because with these for-hire shops no longer counting towards the per-player shop limit, players with this permission can now create an unlimited number of shopkeepers on the server.
  • Command: Add command /shopkeeper setNotForHire (permission shopkeeper.setforhire, same as for the setForHire command) to stop offering one of your shops for hire again and clearing its previously set hire cost item.
  • Fix: Shops that are currently for hire can also no longer be traded with when the UI is attempted to be opened remotely via command or via the API.
  • Fix: Automatically close any currently open hiring UIs when a shop stops being for hire or its hiring cost item changes. Players were already not able to hire these shops via the stale hiring UI before, but now we immediately close the stale UIs.
  • Change: player-shopkeeper-inactive-days restores hired shops of inactive players to their for-hire state instead of deleting them.
• Change: Inform players when the container protection prevents them from interacting with a shop container, breaking it, or placing a block next to it.
• Config: Add enable-left-click-interaction (default: false): If enabled, left clicking (attacking) a shopkeeper mob is handled like a normal mob interaction, i.e. it opens the trading or editor menu.
  • While not officially supported, this may for example be useful for Bedrock players in combination with the Geyser plugin: On Bedrock, not all mobs can be interacted with.
  • This has no effect on block based shop objects such as sign shopkeepers.
  • Metrics: Add the bStats metrics entry enable-left-click-interaction.
• Config: Add max-player-shop-trades-pages (default: 5) to configure the number of trades pages of player shops separately.
  • The previous max-trades-pages setting now only applies to admin shops and the villager editor.
  • Manual migration: If you previously changed the max-trades-pages setting, you will need to manually adjust the new max-player-shop-trades-pages setting accordingly.
• Fix: A player shop's members are cleared now whenever its owner changes, for example via /shopkeeper transfer or when another player hires the shop. Member access granted by the previous owner is not meant to carry over. If the current owner re-hires a shop, the previous members are preserved.
  • Fix: This also resolves that transferring or hiring a shop to one of its own members previously left that player listed as both the owner and a member, which made the shop fail to load.
• Command: /shopkeeper transfer informs the new owner about the received shop now, if they are online.
• Command: /shopkeeper transfer automatically resets the for-hire state of the transferred shop, but preserves the hire cost item, as if the new owner had just hired the shop.
• Fix: When a Citizen NPC player shopkeeper is moved to a different world, the shop containers keep working.
  • Shop containers can technically be located in different worlds now.
  • However, we still prevent players from manually moving their shops to a different world (via the max container distance check), because this can affect the performance.
  • Also, if the delete-shopkeeper-on-break-container is enabled, shopkeepers may still get deleted if the world containing their containers is not loaded currently: We cannot differentiate between worlds being gone for good or only temporarily not available.
• Fix: Trying to create a player shopkeeper in a world different to the world of the selected container resulted in an unhandled exception rather than the intended container distance error message.
• Fix: Shopkeepers are stored more promptly to storage now when they are deleted because their containers got destroyed. We previously marked the storage "dirty", but did not actually trigger a delayed save.
• Fix: Non-flying shopkeeper mobs could not be placed on top of reduced-height blocks such as chests, incorrectly reporting the location as midair.
• Localization: Various messages support hex colors with the &# format now.

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation.

Thanks!

v2.27.0 for MC 26.2, 26.1.2, 1.21.11, 1.21.10, 1.21.8, 1.21.7, 1.21.6, 1.21.5

I only list the primary changes here. For information on API changes, internal changes, and changes to the language files, you can find the complete changelog on Github: https://github.com/Shopkeepers/Shopkeepers/blob/master/CHANGELOG.md

• Update for MC 26.2.
  • Add sulfur cube to the by default enabled mob types.
    • The body equipment slot controls the stored item. However, certain items can result in "visual glitches".
    • Config: Add sulfur-cube-max-size (default: 5). The maximum supported size is 10.
    • On Spigot, the age lock is currently not working (SPIGOT-8139): The mob spawns with a random age and ages until the next respawn / chunk reload.
• Add player shop members: Shop owners can now allow additional players access to their shops.
  • Editor: Add a new option to the editor of player shops to allow owners to view and edit the shop members.
    • Click an empty slot and then enter the name or id of a player to add as shop member into the chat.
    • Left/Right click a member to circle through the different access levels.
    • Shift-click a member to remove them after additional confirmation.
  • Available shop member access levels:
    • Container access.
    • Container and editor access, excluding the ability to view/edit shop members or delete the shop.
    • Full access (same as shop owner): Can also edit the shop members, delete the shop and, depending on the command permissions, manage the shopkeeper snapshots, set the shop for hire, or transfer the shop.
  • Notes:
    • Shop members are taken into account for command completions when the command requires a player name or id.
    • The prevent-trading-while-owner-is-online and prevent-trading-with-own-shop settings also apply to other shop members now: Trading is disabled if any shop member is online and shop members cannot trade with shops they have access to (any access level).
    • If notify-shop-owners-about-trades is enabled, the other shop members also receive trading notifications now.
    • The deleting-player-shop-returns-creation-item also returns the shop creation item to players other than the owner if they have full shop access.
    • The remove-all command and ShopkeeperRegistry#getPlayerShopkeepersByOwner only affects a player's actually owned shops, not shops they have access to.
    • If set-citizen-npc-owner-of-player-shops is enabled: Citizens NPCs only support a single owner, so other players, even with full access, won't be able to edit the Citizens NPC.
    • If a shop member's permission changes, any currently open shopkeeper or container view is automatically closed for them.
    • The editor layout cannot be customized per-player, so the shop members and delete buttons are always visible to all players with access to the editor, but can only be used by players with full shop access.
  • Config: Add setting max-members-per-shop (default: 9).
    • The shop members feature can be disabled by setting this to 0.
    • If the shop members feature is disabled, existing shop members are not automatically deleted from the shopkeeper data, but they are dynamically ignored by the plugin and API.
    • If the limit is reduced, existing shop members are not automatically deleted, but no new members can be edited via the editor.
  • Config: Add setting allow-members-with-full-access (default: true).
    • If disabled, the access level of existing shop members with "full" access is not automatically updated inside the shopkeeper data, but their access level is dynamically downgraded to "edit" access.
  • Config: Add setting members-item to change the editor item.
  • Config: Add setting add-member-item to change the add-member editor item.
  • Config: Config migration 11:
    • Rename prevent-trading-while-owner-is-online to prevent-trading-while-member-is-online.
    • Rename notify-shop-owners-about-trades to notify-shop-members-about-trades.
    • Rename shop-owner-trade-notification-sound to shop-member-trade-notification-sound.
    • Rename debug option owner-name-updates to player-name-updates.
  • Metrics: Add bStats metric uses-shop-members.
• Mannequin shopkeepers use an "Alex" skinned player head now for their profile editor option to not conflict with the new members editor option.
• Fix: Prevent shopkeeper mobs from being sheared by dispensers. Item drops were already prevented before, but other effects on the entity or the dispensed item were not prevented previously.
• Fix: Since the last plugin version, shopkeepers were always marked as "dirty" every time they are loaded, causing a redundant save of all shopkeeper data.
• Debug: Add option shopkeeper-dirty to output additional information whenever a shopkeeper's data is marked as "dirty".

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation.

Thanks!

v2.26.1 for MC 26.1.2, 1.21.11, 1.21.10, 1.21.8, 1.21.7, 1.21.6, 1.21.5

I only list the primary changes here. For information on API changes, internal changes, and changes to the language files, you can find the complete changelog on Github: https://github.com/Shopkeepers/Shopkeepers/blob/master/CHANGELOG.md

• Update for MC 26.1.2.
  • MC 26.1 and 26.1.1 might work but are not officially supported.
• Config: Add setting enable-closing-of-player-shops (default: true) that controls whether shop owners can close their shops.
• Config: Add setting force-open-player-shops (default: true) that controls whether player shops are automatically reopened if enable-closing-of-player-shops is disabled.
  • This setting has no effect if enable-closing-of-player-shops is enabled.
  • Note: Since we do not track whether a shop was closed by the shop owner or the API, this also effectively disables the closing of player shops via the API or when restoring shop snapshots. If you want shops to still be closable via the API or when restoring snapshots, you can temporarily enable this setting after after having disabled enable-closing-of-player-shops, restart the server to update all player shops, and then disable this setting again. However, be aware that the open state in any previously captured shop snapshots is not automatically updated: This setting is only taken into account at the time a snapshot is restored.
  • Debug: When the debug mode is enabled, we log whenever a player shop is forcefully re-opened.
• Fix: Since the last update, mob equipment and default potion effects were no longer applied on spawn.

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation.

Thanks!

v2.25.0 for MC 1.21.11 1.21.10, 1.21.8, 1.21.7, 1.21.6, 1.21.5

I only list the primary changes here. For information on API changes, internal changes, and changes to the language files, you can find the complete changelog on Github: https://github.com/Shopkeepers/Shopkeepers/blob/master/CHANGELOG.md

• Update for Minecraft 1.21.11.
  • Add support for new mob types:
    • Camel husk: Similar editor options as camel.
    • Nautilus: Supports baby variant, saddle and armor.
    • Zombie nautilus: Supports saddle, coral variant and armor.
    • Parched: Similar editor options as other skeleton types.
  • Horse shopkeepers: Add support for netherite horse armor.
• Drop support for Minecraft versions below 1.21.5. This has the following benefits:
  • Modernize the plugin by building against a more modern Bukkit version.
  • Reduce the plugin size by bundling fewer compatibility modules.
  • Simplify updating the plugin for new Paper versions: For versions before 1.21.5, the Spigot and Paper versions shared the same compatibility code, which required building all Paper modules against the Spigot mappings. But since Paper usually releases their Spigot mapping support after some delay, updating the plugin to support the latest Minecraft version on Paper was also delayed.
• Command: Add command /shopkeeper history [player|'all'|'self'] [shop=...|owner=...|'own'|'player'|'admin'|'all'] [page].
  • Permission: shopkeeper.history.own (default: true): Allows viewing the own trading history.
  • Permission: shopkeeper.history.admin (default: op): Allows viewing the trading history of others and admin shops.
  • Example: /shopkeeper blablubbabc shop=Test shows the trading history of player "blablubbabc" with the shopkeeper named "Test" (assuming there is only a single shopkeeper with this name). You can also target a specific shopkeeper via their id, unique id, or by looking at them in-game.
  • The player and owner argument also support the look-up of offline players, taking into account the currently existing shop owners, and existing online mode players. However, the plugin does not check the trading history to find offline players by name.
  • Only the currently existing shopkeepers can be specified by name or id. To look up the trading history of a no longer existing shop, use their unique id.
  • If the owner of a shop has changed, a player without the shopkeeper.history.admin permission can only view the trading history of the shopkeeper from when they still owned the shop.
  • Config: This command is currently only supported when using trade-log-storage: 'SQLITE'.
  • Config: Item metadata (e.g. item display names) can only be retrieved when the trade was logged while using log-item-metadata: true.
  • Debug: If we fail to load the stored item metadata (can for example be the case when there have been backwards incompatible changes across server updates), we log the error in debug mode but otherwise silently ignore it and display the item without the metadata in the history.
  • Trade log: Depending on the trade log merging configuration and the hard-coded IO buffering delay, it can take a few seconds for trades to show up in the trading history. In order for trades to show up in the trading history more quickly, the IO buffering delay (the delay before logs are persisted to the database) is reduced from 30 seconds to 10 seconds. With this change and the default trade log merging configuration, it now takes 10-25 seconds for trades to show up in the trading history, versus the 30-45 seconds from before.
  • In the command output, players have their uuid as hover text and shops have their shopkeeper uuid as hover text.
• Command: The /shopkeeper teleport command shows the shopkeeper uuid as hover text in the success message now.
• Fix: Consider copper chests valid shop containers.
• Fix: Automatically create missing parent directories for the SQLite trade log.
• Fix: Repeat the setup of the SQLite trade log database if an error occurred during a previous save attempt.
• Fix: Baby zombies would occasionally spawn or mount nearby chickens. Disable spawn data randomization.
  • We also cancel any entity mounting events for shopkeeper mobs now, in case there are ever any cases in the future in which mobs might try to mount other mobs, outside of spawning.
• Fix: UnsupportedOperationException during config loading when the missing default value for shop-creation-item is inserted.

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation.

Thanks!

v2.24.0 for MC 1.21.10, 1.21.8, 1.21.7, 1.21.6, 1.21.5, 1.21.4, 1.21.3, 1.21.1, 1.21, 1.20.6

I only list the primary changes here. For information on API changes, internal changes, and changes to the language files, you can find the complete changelog on Github: https://github.com/Shopkeepers/Shopkeepers/blob/master/CHANGELOG.md

• Update for Minecraft 1.21.10.
  • Note: 1.21.9 is not supported and has been superseded by 1.21.10.
  • Update the fallback compatibility module.
  • Add copper golem to the by default enabled mob types.
    • It supports the hand, offhand, head and saddle equipment slots.
    • Its oxidation level is fixed and can be changed via the editor.
  • Add mannequin to the by default enabled mob types.
    • It does not rotate towards nearby players.
    • Equipment is supported but only works with the latest Spigot versions (see SPIGOT-8087).
    • The main hand and pose can be toggled via the editor. Note: Some of the poses have a very small hitbox.
    • We hide the default "NPC" description from the nametag. There is no editor option to customize the description yet.
    • The skin can be specified via the editor by entering the name or uuid of an existing player in chat.
      • On Spigot, the profile lookup by name uses a blocking player id lookup as a workaround for some issue currently (see SPIGOT-8088).
      • There are no editor options yet to customize the profile in other ways or hide individual skin layers.
• Add armor stand to the by default enabled mob types.
  • The editor supports toggling the base plate, arms, and size, as well as equipping items.
• Config: Changes to the item data format inside the config.
  • The new format aligns more closely with how Minecraft represents item data and how we represent item data inside the save file.
  • We now use Minecraft's item type ids instead of Bukkit's material names.
  • Additional item data components are represented in SNBT.
  • Example:
    Old:

    shop-creation-item:
      type: VILLAGER_SPAWN_EGG
      display-name: '{"text":"Shopkeeper","italic":false,"color":"green"}'

    New (1.20.5+):

    shop-creation-item:
      id: 'minecraft:villager_spawn_egg'
      components:
        minecraft:custom_name: '''{"color":"green","italic":false,"text":"Shopkeeper"}'''

    New (1.21.5+): SNBT instead of JSON for text data.

    shop-creation-item:
      id: 'minecraft:villager_spawn_egg'
      components:
        minecraft:custom_name: '{color:"green",italic:0b,text:"Shopkeeper"}'

  • Your existing config is automatically migrated to the new format.
  • Add new setting data-version: This setting is automatically updated whenever you migrate to a new server version and used to automatically migrate your item data inside the config.
  • We no longer convert between legacy and alternative color codes. For recent Minecraft versions, the use of Minecraft's JSON / SNBT text representation is recommended.
• Config: Changes to how we compare the data of config items such as the shop creation item.
  • Previously, we tried to emulate Minecraft's NBT data matching based on Bukkit's item serialization output. This approach was not ideal: Bukkit's item serialization comes with overhead and its output does not perfectly match Minecraft's item NBT structure. And on recent versions of the Paper server, the Bukkit item serialization has been deprecated and might no longer receive updates.
  • The item matching implementation was updated to directly use Minecraft's underlying NBT comparison logic.
  • However, this also means that this logic is now part of the plugin's Minecraft version specific code that must be updated for every new version of Minecraft. A reflection based fallback implementation is available for Spigot servers, but is likely to break across server updates as well.
  • To more closely align with Minecraft's NBT matching logic used in commands and by the custom_data predicate, we also match partial lists now. Previously, we would not match partial lists to more closely align with how items are compared in villager trades. But in newer versions, the item comparison in villager trades has become more strict. And for the matching of config items, we prefer a more lenient partial matching of item data.
• Data: Remove the item conversion feature.
  • This feature was used as a workaround in the past to help server owners deal with changes to the internal item data representation across server versions. Since then, there have been changes in Spigot to better preserve text data during serialization. And with the introduction of item data components in MC 1.20.5 and the changes to how Minecraft itself normalizes and compares item data now, this feature should no longer be required. Also, especially on Paper servers, this feature might break items since it relies on Bukkit's serialization and deserialization of ItemMeta, which is deprecated on Paper servers.
  • Command: Remove command convertItems and related permissions shopkeeper.convertitems.own and shopkeeper.convertitems.others.
  • Debug: Remove debug option item-conversions.
  • Config: Remove settings convert-player-items, convert-all-player-items and convert-player-items-exceptions.
• Data: Use default salmon variant if missing.
• Fix: Shopkeeper mobs no longer equip items from dispensers.
  • These equipment items are not persisted and permanently lost once the shopkeeper is respawned. Instead, use the shopkeeper editor to add equipment to shopkeeper mobs.

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation.

Thanks!

In reply to shadowsoul3838:

 No, this plugin only support item trades. It does not work with virtual currencies and it does not use any of Minecraft's scoreboard features.

v2.23.10 for MC 1.21.8, 1.21.7, 1.21.6, 1.21.5, 1.21.4, 1.21.3, 1.21.1, 1.21, 1.20.6

I only list the primary changes here. For information on API changes, internal changes, and changes to the language files, you can find the complete changelog on Github: https://github.com/Shopkeepers/Shopkeepers/blob/master/CHANGELOG.md

• Update for MC 1.21.8 (Paper support).

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation.

Thanks!

In reply to powerofx6557_31599:

 You need to use an older plugin version for that. Try 2.22.3: https://dev.bukkit.org/projects/shopkeepers/files/5569421

v2.23.9 for MC 1.21.7, 1.21.6, 1.21.5, 1.21.4, 1.21.3, 1.21.1, 1.21, 1.20.6

I only list the primary changes here. For information on API changes, internal changes, and changes to the language files, you can find the complete changelog on Github: https://github.com/Shopkeepers/Shopkeepers/blob/master/CHANGELOG.md

• Update for MC 1.21.7.
• Data: Minor internal changes to item serialization and handling of deserialization issues.

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation.

Thanks!

v2.23.7 for MC 1.21.6, 1.21.5, 1.21.4, 1.21.3, 1.21.1, 1.21, 1.20.6

I only list the primary changes here. For information on API changes, internal changes, and changes to the language files, you can find the complete changelog on Github: https://github.com/Shopkeepers/Shopkeepers/blob/master/CHANGELOG.md

• Update for MC 1.21.6.
  • Add happy ghast to the by default enabled mob types.
    • It supports a baby variant and a colored harness can be equipped to its body slot.
    • It does not seem to look at players currently when turned to its baby variant or back.
  • Update the fallback implementation.
• Config: Avoid inserting default settings if the loaded config data is completely empty.
  • The config data can also be empty if the config file failed to load. Inserting the default settings in this case would overwrite the user's current config.
  • To reset the config to its default values, it is now required to fully delete the config file. Only clearing the config file is not longer sufficient.

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation.

Thanks!

v2.23.6 for MC 1.21.5, 1.21.4, 1.21.3, 1.21.1, 1.21, 1.20.6

I only list the primary changes here. For information on API changes, internal changes, and changes to the language files, you can find the complete changelog on Github: https://github.com/Shopkeepers/Shopkeepers/blob/master/CHANGELOG.md

• Data: Change the serialization of item stacks from Bukkit's built-in serialization to a custom serialization that saves item components as SNBT. Be sure to backup your current save.yml file before updating to this version!
  • This has the following expected benefits:
    • Better debugging of serialized item data: The data is serialized in a format that Minecraft users are familiar with and can find information about in the official Minecraft wiki.
    • Better compatibility across Minecraft server versions: We pass the deserialized data through Minecraft's own data migration system, which should hopefully reduce the need for manual data migrations after server upgrades.
    • Better compatibility across server variants: Spigot and Paper servers have diverged in how they serialize item stacks. Paper already saves item stacks in a format similar to the one used by the Shopkeepers plugin now. But by not relying on the specific server's built-in serialization, saved item data is expected to more easily be transferable across server variants.
  • The shopkeeper storage version is bumped to 4 to automatically write all item data in the new format.
  • The new serialization relies on server version specific code. A reflection-based implementation for Spigot mappings is provided for the "fallback mode" when running on a non-supported server version, but this is prone to break during server updates.
  • Since all item data is migrated via Minecraft's data migration now, before the item stack is constructed, our previous item data migration logic can eventually be removed, together with the item-migrations debug option, once all servers are expected to have updated to the new serialization format.
• Fix #959: The changes to the shopkeeper trade event in v2.19.0 introduced a bug that caused shift trading to continue trading even if the the active trade switches to a different result item. Additionally, we now also abort the trading if the cost items of the active trading recipe have changed, so that players don't accidentally continue trading the same result item but for different costs.
• Localization: Use the default message when the specified language file is missing an entry.
• Debug: Log the full exception stack trace when we fail to load the data of a shopkeeper.
• Debug: The fallback mode can now be tested by adding a file with name .force-fallback to the plugin folder.
• Internal: Various refactors related to UIs.
• API: Revert nonpe version back to 1.3.5 for now until 1.3.6 has been released to Maven central. This resolves an issue with API clients being required to also add the nonpe snapshot repository to their projects.

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation.

Thanks!

In reply to Creeperboy402:

 I don't know. If they allow you to upload plugin jars manually, you can download it here and upload it to the server. If they don't support that, you have to check their repository and ask their support.

v2.23.5 for MC 1.21.5, 1.21.4, 1.21.3, 1.21.1, 1.21, 1.20.6

I only list the primary changes here. For information on API changes, internal changes, and changes to the language files, you can find the complete changelog on Github: https://github.com/Shopkeepers/Shopkeepers/blob/master/CHANGELOG.md

• If available, use the item's custom display name in trade notification messages.
• Performance: Further optimize the handling of the BlockPhysicsEvent for sign shopkeepers: Instead of checking during each block physics event whether the event shall be cancelled because the block or one of its neighbors would be affected by the event (7 checks), we pre-calculate the set of affected block locations and then only perform a single map lookup during the event (1 check).
• Performance: Optimize shulker peek AI: Only update the peek state if actually necessary to avoid redundant game events and other side effects.
• Performance: Remove the PlayerMap "optimization" again: It does not provide a clear benefit, but adds additional complexity and potential for bugs and memory leaks.
• Fix: It was still possible to spawn or move shopkeepers into protected GriefPrevention regions. When using the check-spawn-location-interaction-result, we now temporarily spawn a dummy chest block at the checked location to ensure that region protection plugins like GriefPrevention actually react to our dummy interaction test event.
• Fix: Mark shopkeepers as dirty when a property value is found missing and the default value is being used.
  • As before, we log a warning and then fall back to the default value for missing property values. This is for example often the case when new properties are added.
  • However, previously, we would not mark the shopkeeper as dirty in this case since the default value also equals the initial property value. One consequence of this was that the warning about missing property values would be repeated over and over during subsequent plugin reloads.
• Fix: Add a Paper-specific 1.21.5 module to resolve issues related to trade notifications and pig, cow and chicken variants.
• Paper: Omit redundant 'id' and 'count' properties when logging the metadata of items involved in trades.

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation.

Thanks!