Плагин shopkeepers как настроить

Bukkit

Shopkeepers

Bukkit Plugins

Shopkeepers

Table of Contents

Set up custom villager shopkeepers that sell exactly what you want them to sell and for what price. You can set up admin shops, which have infinite supply, and you can also set up player shops, which pull supply from a chest.

It will also prevent any other trades with non-shopkeeper villagers, if you want it to.

For those who are simply looking for a convenient way to modify the trades of vanilla villagers (as an alternative to using complex Minecraft commands), the plugin also includes a graphical editor for regular villagers and wandering traders.

Basic Features

• Easily create villager shopkeepers that trade the items you want them to trade.
• Admins shops with infinite supplies.
• Player shops which pull supplies from a chest.
• Different types of player shops: selling, buying, trading, and selling books.
• Various supported mob types to represent your shopkeeper, sign shops, and Citizens (NPC) shops.
• Editor for regular villagers and wandering traders.
• Many configuration options.
• Translatable messages.
• Open source (Source code on GitHub)

Supported server versions

Shopkeepers supports the latest versions of Bukkit / Spigot .
Note that this plugin is created to work with CraftBukkit (or alternatively Spigot). Bukkit does not have an API for some of the things necessary to make this plugin work. This means that other server software (Tekkit, Forge, Cauldron, etc.) will not work with this plugin.
Other CraftBukkit or Spigot derivatives/forks might work, but are not officially supported. So if you run into issues while using those, try to reproduce your issue on a fresh and up-to-date Spigot server first.

Getting started

All documentation can be found in the wiki :

Showcase

Admin shops:

Configure the trades via the in-game inventory menu:

Resulting trading menu:

Player shops (ex. selling items):

Fill the shop chest with supplies:

Configure the trades via the in-game inventory menu:

Resulting trading menu:

Video Tutorials

Tutorial by Donnie, explaining the setup of the different shop types:

Tutorial by Fan Staaff showing the setup of the different shop types in detail:

Tutorial by Dovamero , also showing the setup of the different shop types and some configuration:

Spanish tutorial by Ajneb97 , also mentioning placeholder items and various config options:

Statistics

This plugin uses bStats to collect anonymous plugin usage statistics. This helps me to determine how many servers are using the plugin, which Minecraft versions it is used with the most, and to which degree the different features are used.

Here is a list of all currently tracked information:

• Common information: The number of servers using the plugin, the number of players on these servers, online mode, Minecraft version, plugin version, core count, system arch, operating system, server country, Java version.
• Shopkeepers specific information: Whether specific related plugins are used (Citizens, Towny, WorldGuard, Gringotts, other Vault economy plugins), number of shops, whether player shops are used, whether certain features are enabled in the config (ex. WorldGuard/Towny compatibility, Citizens shops, delayed saves, colored names, chest protection, removal of inactive shops, tax rate, strict item comparison, purchase logging, disabling of other villagers, ..), the number of worlds containing shops.
• All information can be publicly viewed here: https://bstats.org/plugin/bukkit/Shopkeepers/

If you want to disable bStats for all plugins on your server, edit the file plugins/bStats/config.yml, or alternatively disable it only for Shopkeepers by setting ‘enable-metrics‘ to ‘false‘ inside the Shopkeepers config.

Known potential issues

A list of known potential issues of the latest version of Shopkeepers can be found in the wiki: This documents differences between Minecraft/Spigot versions, and existing Minecraft/Spigot issues related to Shopkeepers.

If you run into an issue, check if this list already contains and maybe offers information on how to handle it.

Have issues or further questions?

If you have a pressing issue or simple question, you can join the discord server and ask other plugin users for help:

But submitting a ticket is the best way to get help or report a problem with the plugin.

Before submitting a ticket:

• Check if your question is already answered in:
  • The documentation (wiki) .
  • The FAQ .
  • The Known Issues .
• Check if there is already another ticket for your issue.

Before reporting an issue:

• Try to reproduce your issue when using:
  • The latest versions of Spigot and Shopkeepers.
  • No other plugins.
  • No kinds of other server or client mods.

When reporting an issue:

• Provide the versions you are using of Minecraft, Spigot and Shopkeepers.
• Provide a detailed description of your problem and add as much information as possible which could help reproducing the issue.
• If possible, include step-by-step instructions on how to reproduce the issue on a fresh Spigot server.

Donations

If you like this plugin, consider supporting its developers by making a donation:

• To blablubbabc (current maintainer: Dec 2013 — today)
• To nisovin (former author: Aug 2012 — Dec 2013)

A big «thank you» to everybody who is keeping the motivation up through donations!

Minecraft-Servers-Listing.com	TRS Game Servers	terminalserver.us
Minewind	mercurialmusic	timitimitimi
FatherWh0 (merchantvillages.com)	lukeeexd (tws-mc.com)	PapaJuan
EmeraldHaze (Ninjalette)	Espen	kbtalkin
Dimo (Beyond Vanilla)	RefugiaCraft	Frilioth

Want to help?

The less I have to do myself, the more time I have to write plugins. Therefore I am looking for someone who would be willing to get involved in the project. That could for example mean:

• Keeping the documentation (the wiki) up-to-date with plugin updates.
• Improving the existing documentation.
• Creating and maintaining translations.
• Help managing issues and answering questions of users.

If you are a programmer with experience in writing bukkit plugins, or have ideas on how you can contribute to the project beyond that, let me know as well! If you are interested, feel free to contact me via PM.

Beyond that, everybody is invited to help others with issues and questions in the issue tracker, comment section, and the discord channel! Also consider contributing translations !

Comments

li» data-page-inline=»False» data-scroll-inline=»False» >

• Join Date: 5/29/2012
• Posts: 3,122
• Member Details

• Join Date: 6/6/2021
• Posts: 24
• Member Details

Can this realize the functions of «transmitting», «information» and «giving goods»?

• Join Date: 5/29/2012
• Posts: 3,122
• Member Details

I don’t know what you mean by that. You can setup predefined trades: 1 or 2 stacks of items provided by a player are exchanged for 1 item stack given to the player. Nothing more.
You can not setup trades that don’t require at least one input item.

• Join Date: 7/19/2021
• Posts: 1
• Member Details

Is there a way to teleport the shopkeeper with commands/command block or is it not possible yet?

• Join Date: 5/29/2012
• Posts: 3,122
• Member Details

Not possible yet.

• Join Date: 5/29/2012
• Posts: 3,122
• Member Details

v2.13.3 for MC 1.17.1, 1.17, 1.16.5, 1.15.2, 1.14.4

• Fixed: The ‘style’ property of horse shopkeepers was not getting saved anymore since v2.13.0 and caused migration warnings whenever the plugin attempted to load or save it. If you already upgraded, and don’t have a backup of your save.yml file available, or don’t want to revert to the backup’s state, you may have to freshly edit the ‘style’ of your horse shopkeepers again.
• Fixed: There is an open Spigot 1.17 issue that sometimes causes the plugin to assume that it failed to spawn shopkeepers during chunk loads. In v2.13.1, we already turned a warning message related to this into a debug message in order to not spam the server log with warnings. But another message was missed and has now been turned into a debug message as well.

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation .

• Join Date: 7/8/2021
• Posts: 3
• Member Details

How do I enable a shopkeeper? I’ve tried and I’ve looked here but I can’t find out how

• Join Date: 5/29/2012
• Posts: 3,122
• Member Details

What do you mean with ‘enable’`? If the plugin was installed and was able to enable, you can create shopkeepers as described in the wiki: https://github.com/Shopkeepers/Shopkeepers-Wiki/wiki/Creating-Shops#shop-creation

• Join Date: 7/8/2021
• Posts: 3
• Member Details

I tried to have a shulker as a shopkeeper and it said they weren’t enabled, so how would I fix that? Thanks:)

• Join Date: 5/29/2012
• Posts: 3,122
• Member Details

Add ‘ SHULKER ‘ to the list of ‘ enabled-living-shops ‘ inside the config.

• Join Date: 7/8/2021
• Posts: 3
• Member Details

• Join Date: 5/29/2012
• Posts: 3,122
• Member Details

v2.13.2 for MC 1.17.1, 1.17, 1.16.5, 1.15.2, 1.14.4

• Updated for MC 1.17.1
• Building: Bumped the CraftBukkit dependencies for the 1_16_R2 and 1_16_R3 versions of Shopkeepers from 1.16.2-R0.1 and 1.16.4-R0.1 to 1.16.3-R0.1 and 1.16.5-R0.1 respectively. This has no effect on the server versions the plugin works on, but simplifies testing.
• Internal: We now use the server’s mappings version to check if the plugin is compatible.
  • Previously, we used CraftBukkit’s ‘Minecraft Version’ to determine compatibility (eg. ‘1_16_R3’ for 1.16.5). However, Spigot will occasionally update its mappings without bumping the CraftBukkit version or this ‘Minecraft Version’. With the new remapping of NMS code since 1.17, these mappings changes will forcefully break our compiled NMS code and then require an update (or at least a rebuild) of the Shopkeepers plugin.
  • Previously, these mappings changes would result in errors during plugin startup, instead of being detected as an incompatible server version. We now keep track of all supported mappings versions and use the server’s mappings version to determine whether we can support it and which NMS module we need to load.
  • For some of the 1.16 versions of the plugin, multiple mappings versions are mapped to the same NMS module. However, this should not be a problem, because these modules do not make use of the new remapping build feature, and are therefore less likely to actually break on mappings changes (there are no known server incompatibility issues for these versions).
  • Another effect of the mappings versions being changed without there necessarily being a CraftBukkit version bump: Since our NMS modules build against specific CraftBukkit versions instead of mappings versions, we can only support the latest mappings version for every CraftBukkit version.
  • Building: Added test cases to ensure that our NMS modules build against CraftBukkit versions with the expected mappings versions.
  • Also, our NMS module versions no longer have to match CraftBukkit’s ‘Minecraft Version’. In order to be able to support different mappings versions even if Spigot does not bump its ‘Minecraft Version’ (as it was the case in the 1.17 to 1.17.1 update), we will now derive a new NMS module version by incrementing the revision number ourselves.
• Fixed: The compatibility mode when running on an unsupported server version was no longer working.
• If the compatibility mode fails to enable, we now log an error that should provide additional information about the issue.
• Fixed: When the compatibility mode failed to enable, we would encounter an error during plugin disable due to the TradeLoggers component not having been enabled yet.
• Bumped Citizens dependency to v2.0.28.
• Config: Added setting ‘save-citizen-npcs-instantly’ (disabled by default), which triggers a save of all Citizens NPC data whenever the Shopkeepers plugin modifies a Citizens NPC. Saving the Citizens NPCs is quite a heavy operation. Since the Citizens API does not yet provide an API to trigger an asynchronous save, we trigger the asynchronous save by invoking the «/citizens save -a» command in the console. As a side effect, this will print command feedback in the console whenever the NPCs are saved this way.
• Fixed: Since v2.13.0, when not using the ‘always-show-nameplates’ setting (i.e. the default case), the nameplates of Citizens player NPC shopkeepers were limited to a length of 16 and would otherwise not be displayed. The issue is that the Citizens ‘hover’ nameplate option does not work well for player NPCs. If you are upgrading and have issues with nameplates of previously created NPCs not showing, either use the shopkeeper editor to rename the NPC, or use the «/npc name» command to toggle the nameplate visibility.
• We no longer open the trading interface if the shopkeeper has no offers. If the player can edit the shopkeeper, we print instructions on how to open the editor. This may also resolve an incompatibility with Bedrock players when using GeyserMC.
• Fixed: Writing files (such as when saving the shopkeepers data) failed on some servers due to the SecurityManager implementation blindly denying the execute permission without differentiating between files and directories. We check the execute (i.e. access) permission for directories in which we want to write files in order to provide more meaningful error messages in cases in which missing directory permissions prevent us from writing files. However, this intervention of the SecurityManager should have no effect on whether or not we can actually write to a directory, so we can safely ignore it.
• API: Added Shopkeeper#hasTradingRecipes(Player).
• API: The type parameters of TypeRegistry#registerAll and #getRegisteredTypes were changed to be less specific.
• Debug: When we print ItemStacks in YAML representation to the server console, we omit the trailing newline now. However, the «/shopkeeper yaml» command still sends additional empty lines in chat to make the output more readable.
• Debug: Added debug option ’empty-trades’ that logs item information for the selected trading recipe and the input items whenever a player clicks an empty trading result slot.
• Internal: We avoid copying item stacks in a few more cases.
• Internal: Renamed MerchantUtils#getSelectedTradingRecipe() to #getActiveTradingRecipe() and adjusted a few related debug messages.
• Internal: Various refactors related to the default UIs, time unit conversions, and utilities in general.

Known potential issues: See here.

Donations

If you like this plugin, consider making a donation .

Источник