Test Shopkeepers buying trades with enchanted and damaged items

Applies to: Shopkeepers; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

Buying shops need careful item matching. Vanilla trade behavior can accept or reject variants in ways an owner did not expect, so test valuable equipment before advertising a buy offer.

Before you start

Shopkeepers player trades exchange physical items held in a linked container. A Vault balance is not the stock for these trades. Work with the shop owner and keep the container, shop record and item metadata together when investigating a failure.

Work through the check

Record the buying recipe, including the example item and currency quantity, and use an isolated shop stocked only for a few low-value tests.
Prepare separate plain, damaged, enchanted and renamed samples relevant to the item, labeling their differences outside the trade inventory.
Try each sample with a normal customer account and record which variants the current release accepts; inspect the resulting item in the owner’s chest.
Check the maintainer’s buying-shop matching notes before changing the example item. Avoid assuming every name or enchantment creates a strict distinction.

Confirm the result

You should have a written acceptance matrix for the recipe before using it with expensive player items. Each accepted variant must produce the intended payment and reach the owner’s container.

If the result differs

Vanilla matching can be asymmetric: a plain requirement may accept a more decorated item. A visual preview alone does not prove that enchanted or cursed equipment is excluded.

Recover safely

Disable the affected offer through the supported editor until its acceptance rules are suitable. Preserve original sample items and restore the previous recipe rather than deleting the shop or its container.

Documentation and related help

Check the Shopkeepers maintainer documentation and Shopkeepers maintainer reference against your installed release before applying changes.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report