Unofficial site, not affiliated with modrinth.com.What is this?
  • EzShops 2.5.6

    release22 мая 2026 г.

    Through time we've made the stock market more stable, by doing this the documentation got outdated and configuration options that existed before got phased out. This version there was focus on updating the documentation and adding back options that got phased out in a more stable way.

    Added

    • Configurable stock price-engine parameters - volatility-min, volatility-max, demand-multiplier, min-price, and update-interval are now real config.yml options under the stock: section. The plugin reads them on startup and applies them to the price engine. All defaults match the previously hardcoded values so existing behaviour is preserved.

    Fixed

    • Incorrect stock-market configuration documented - docs/configuration/main-settings.md and docs/shops/pricing/stock-market.md previously documented a non-existent stock-market: config block. Both pages now document the real stock: section (enabled, cooldown-millis, blocked, overrides, categories). Price-engine parameters (volatility-min, volatility-max, demand-multiplier, min-price, update-interval) are now implemented as real config options (see Unreleased → Added).
    • /sell command missing from documentation - the Quick Sell GUI command (/sell) is now documented in the Commands reference with its behavior and permission node.
    • /shopadmin command missing from documentation - /shopadmin [browse|market] is now documented under Admin Commands including both the player-shops and team-market views.
    • /teamshop market subcommand missing from documentation - the team P2P market subcommand is now documented in Commands, the TeamsAPI integration page, and the tab-completion list for /teamshop.
    • Missing permission nodes in documentation - the following nodes were present in plugin.yml but absent from the Permissions reference; they are now documented:
      • ezshops.shop.admin (open /shopadmin GUI)
      • ezshops.teamshop.market (access team P2P market)
      • ezshops.pricing.admin.set, ezshops.pricing.admin.disable, ezshops.pricing.admin.list (granular pricing-admin nodes)
  • EzShops 2.5.5

    release18 мая 2026 г.

    Fixed

    • on-sell commands not executing for item-type: COMMAND itemssell() no longer checks or removes physical items from the player's inventory when the item's delivery type is COMMAND. Previously the transaction exited early with "insufficient items" because the player had no material to hand over, preventing sell commands from running at all.
    • on-sell execute-as overridden by on-buy execute-asShopPricingManager now tracks execute-as independently for the on-buy and on-sell blocks. Previously a single shared flag meant that setting on-buy: execute-as: player would silently override on-sell: execute-as: console, causing sell commands to run as the player instead of the console.

    Added

    • Code coverage reporting — JaCoCo is now configured in the Maven build (jacoco-maven-plugin 0.8.12). Coverage reports (jacoco.xml) are generated on every mvn test run and uploaded to Codecov by the CI workflow for both unit-test and feature-test jobs.
  • EzShops 2.5.4

    release16 мая 2026 г.

    Fixed

    • Quick Sell GUI "Nothing to sell" after shift-clickhandleConfirm now calls a new ShopTransactionService.sellDirect() method that skips the player-inventory item count/removal steps. Previously, shift-clicking items into the GUI moved them out of the player's inventory, so the old sell() path found zero items and reported nothing to sell.
    • Quick Sell GUI shows "Nothing to sell" when sell fails after shift-clickhandleConfirm now distinguishes between a genuinely empty GUI and a GUI that has items but whose sellDirect call failed (e.g. economy down, dynamic price driven to $0.00 by a previous sale, rotation expired). The actual failure reason is shown to the player instead of the misleading "No items to sell." message. Items that failed to sell remain in the GUI so the player can retry.
    • Quick Sell GUI rejects rotation items even when directly sellablesellDirect and isSellable both applied a rotation-visibility check that belongs only in the main shop menu. The Quick Sell GUI is designed to accept any item with a configured sell price; rotation restrictions are now only enforced in sell(), which is the path used when a player types /sell or /sellhand.
    • Legacy shop.yml item keys not found when using lowercase material namesloadLegacyEntries now normalises every price key to Material.name() (e.g. BIRCH_LOG) before registering it in the price map. Previously, a config entry written as birch_log: was stored under the lowercase key, so getPrice(Material.BIRCH_LOG) could not find it, silently treating the item as unpriced.

    Added

    • Stripped log variants in the wood category — all 9 stripped log types (STRIPPED_OAK_LOG, STRIPPED_SPRUCE_LOG, STRIPPED_BIRCH_LOG, STRIPPED_JUNGLE_LOG, STRIPPED_ACACIA_LOG, STRIPPED_DARK_OAK_LOG, STRIPPED_MANGROVE_LOG, STRIPPED_PALE_OAK_LOG, STRIPPED_CHERRY_LOG) are now included in the default wood.yml config so players can sell stripped logs with /sellhand and the Quick Sell GUI out of the box.
    • Wood (all-bark) block variants in the wood category — all 9 wood block types (OAK_WOOD, SPRUCE_WOOD, BIRCH_WOOD, JUNGLE_WOOD, ACACIA_WOOD, DARK_OAK_WOOD, MANGROVE_WOOD, PALE_OAK_WOOD, CHERRY_WOOD) are now included. Previously, attempting to /sellhand a "Birch Wood" block (as opposed to a "Birch Log") would return "That item is not configured in the shop."
    • Plank variants in the building category — all 9 plank types (OAK_PLANKS, SPRUCE_PLANKS, BIRCH_PLANKS, JUNGLE_PLANKS, ACACIA_PLANKS, DARK_OAK_PLANKS, MANGROVE_PLANKS, PALE_OAK_PLANKS, CHERRY_PLANKS) are now included in the default building.yml config.
  • EzShops 2.5.3

    release14 мая 2026 г.

    Fixed

    • TeamTreasury transaction safetydeposit now refunds the player's Vault balance if the YAML save fails, preventing money from being lost on a failed write. withdraw debits the treasury before paying the player so a failed save aborts the operation without creating currency from nothing.
    • TeamStockManager negative-amount guardremoveTeamStock now returns false immediately when amount <= 0, preventing invalid stock mutations.
  • EzShops 2.5.2

    release12 мая 2026 г.

    Fixed

    • TeamsAPI optional integrationNoClassDefFoundError no longer crashes plugin startup when TeamsAPI is absent from the classpath. The availability check is now wrapped in a NoClassDefFoundError catch block so the integration degrades gracefully whether the JAR is missing entirely or the plugin is simply not loaded.
  • EzShops 2.5.1

    release12 мая 2026 г.

    Added

    • Folia support — EzShops now runs on Folia servers. All scheduler calls are routed through a new SchedulerAdapter that transparently delegates to GlobalRegionScheduler / AsyncScheduler on Folia and to BukkitScheduler on Paper/Spigot/Bukkit. The folia-supported: true flag has been added to plugin.yml.

    Changed

    • EzBoost engine improvement — reflective access to EzBoost's price-multiplier API is now cached after the first lookup. Class.forName, getMethod, and getPlugin are no longer called on every transaction; instead, resolved Method references are reused for the lifetime of the server.
  • EzShops 2.5.0-nightly.20260511

    beta11 мая 2026 г.

    Notes

    🌙 Automated nightly beta build from main (May 11, 2026).

    Built from b711ac3

  • EzShops 2.5.0

    release11 мая 2026 г.

    This version we focussed on adding Team Shops, a full team-based economy layer built on top of TeamsAPI. Teams get their own market, shared treasury, stock pool, and role-based pricing, all accessible through a new /teamshop command.

    Team Market GUI

    Added

    • TeamsAPI integration — EzShops now integrates with TeamsAPI as a soft dependency; all features degrade gracefully when TeamsAPI is absent.
    • Role-based sell multipliers — MEMBER, ADMIN and OWNER each receive a configurable sell price bonus when selling to the shop (teams-integration.sell-multiplier in config.yml).
    • Role-based buy discounts — MEMBER, ADMIN and OWNER each receive a configurable buy price reduction when purchasing from the shop (teams-integration.buy-discount in config.yml).
    • Team treasury — a shared balance funded automatically by a configurable percentage of every sell transaction (teams-integration.treasury-split). Members can deposit and withdraw funds through the treasury GUI.
    • Shared team stock — stock quantities are pooled per team; all members draw from and contribute to the same pool (teams-integration.shared-stock).
    • /teamshop command — opens the team shop dashboard showing team info, current multipliers and quick links.
      • /teamshop treasury — opens the team treasury GUI (deposit / withdraw; requires ezshops.teamshop.treasury.withdraw).
      • /teamshop stocks — browse all items your team currently has in stock.
    • Permissions:
      • ezshops.teamshop (default: true) — access the team shop dashboard.
      • ezshops.teamshop.treasury.withdraw (default: true) — withdraw from the team treasury.
      • ezshops.teamshop.admin (default: op) — administrative team stock commands.
    • Automatic data cleanup — team stock and treasury data are deleted automatically when a team is disbanded via the TeamDeleteEvent.
  • EzShops 2.4.2

    release7 мая 2026 г.
  • EzShops 2.4.1

    release4 мая 2026 г.
    • Fixed issue: Bukkit's getMinecraftVersion() >= 14 failed because of new 26.1 version format
  • EzShops 2.4.0

    release3 мая 2026 г.

    What's Changed

    Quick Sell GUI

    Full Changelog: https://github.com/ez-plugins/EzShops/compare/2.3.1...2.4.0

  • EzShops 2.3.1

    release26 марта 2026 г.
  • EzShops 2.3.0

    release25 марта 2026 г.

    New /pricingadmin command

    • Added new /pricingadmin command for managing the shop prices
      • Added /pricingadmin set <item> <price> subcommand with ezshops.pricing.admin.set permission for setting the price of an item in the shop
      • Added /pricingadmin reset <item> subcommand with ezshops.pricing.admin.reset permission for resetting the dynamic pricing of an item in the shop
      • Added /pricingadmin resetall subcommand with ezshops.pricing.admin.resetall permission for resetting all dynamic prices of the shop

    New /shop <category> subcommand

    • Added /shop <category> subcommand to open category GUIs directly
    • Added missing configurable messages

    What's Changed

    New Contributors

    Full Changelog: https://github.com/ez-plugins/EzShops/compare/2.2.3...2.3.0

  • EzShops 2.2.3

    release2 марта 2026 г.

    This version is for so far untested. Use 2.2.2 as stable version for now.

    Changes

    • (#34) Added buy price discount boost for EzBoost integration (by matheusherman)
    • (#35) Added multi language not-in-rotation message
    • (#35) Added new check for each buy/sell feature and if item is not available, but sometimes is in rotation send this new message instead of actually still buy/selling.
  • EzShops 2.2.2

    release10 февраля 2026 г.
    • New NBT filter options for sell prevention ( by @matheusherman in #27 )
      • Added NBT data whitelist
      • Added NBT data blacklist

    Default config.yml settings

    sell:
      # Ignore items with NBT (custom tags/metadata) during /sellhand and /sellinventory
      # When enabled, only plain items without NBT will be sold.
      # For example: if you have a "Supreme Bone" (with NBT) and normal bones,
      # only the normal bones will be sold when using /sellinventory.
      # Default: false
      ignore-items-with-nbt: false
    
      # NBT tag filter for more granular control
      # Mode: 'off', 'whitelist', or 'blacklist'
      #   - 'off' (default): Ignore the filter, use ignore-items-with-nbt setting only
      #   - 'whitelist': Only allow items with NBT tags in the whitelist
      #   - 'blacklist': Block items with NBT tags in the blacklist
      nbt-filter:
        mode: "off"
        whitelist: []
        blacklist: []
    
  • EzShops 2.2.1

    release8 февраля 2026 г.
    • Added item-type option to make it easier to prevent normal shop execution
      • ITEM — Default. The player receives the configured ItemStack when they buy the item.
      • COMMAND — The player is charged and pricing/dynamic effects are applied, but no ItemStack is given. Any configured on-buy commands (or buy-commands) will be executed.
      • NONE — The player is charged and pricing/dynamic effects are applied, but no ItemStack is given and no commands are executed. Useful for non-physical purchases (tokens, permissions, etc.).
  • EzShops 2.2.0

    release31 января 2026 г.
    • Added toggle in configuration to disable player-shop protection
    # When true, other players cannot open or break player shop chests/signs.
    # Set to false to allow other players to open the chest and break the sign.
    protection-enabled: true
    
    • Added automated testing in Github project
    • Added CI to run feature and unit tests when pull request is created in Github project
    • Added CI to validate YML configuration files in Github project
  • EzShops 2.1.3

    release30 января 2026 г.
    • Fixed typing quantity in chat for creating new /playershop
    • Fixed typing price in chat for creating new /playershop
  • EzShops 2.1.2

    release29 января 2026 г.
    • Improved pagination logic
    • Added preserve-last-row option to preserve the row with actions for the actions only
    • Added pagination documentation
    • Added command autocomplete for configured price-ids to show when using /shop buy <material> and /shop sell <material>
  • EzShops 2.1.1

    release29 января 2026 г.

    Per-item price keys (price-id) (optional)

    To allow multiple independent price entries for the same Minecraft Material (for example two different shop items that both use EXPERIENCE_BOTTLE), items may declare an optional price-id string in their configuration. When present, the plugin uses this price-id as the pricing key (and as the dynamic-pricing state key stored in shop-dynamic.yml) instead of the material name.

    Notes:

    • price-id is optional; if omitted the material name (e.g. DIAMOND, EXPERIENCE_BOTTLE) is used and pricing remains material-scoped (backwards compatible).
    • price-id must be unique across your shop configuration if you want independent pricing/multipliers for two items that share the same material.
    • Dynamic state (multipliers) are saved by price-id in shop-dynamic.yml when present; legacy material keys continue to be supported.

    Example (category item):

    my-exp-bottle-item:
    material: EXPERIENCE_BOTTLE
    price-id: exotic_exp_1   # optional unique key to separate pricing
    buy: 10.0
    sell: 5.0
    dynamic-pricing:
      starting-multiplier: 1.0
      min-multiplier: 0.5
      max-multiplier: 3.0
      buy-change: 0.01
      sell-change: 0.01
    
1

Совместимость

Сведения

Лицензия:
Опубликован:5 месяцев назад
Обновлён:3 недели назад
ID проекта:
Главная