QuickShop-Hikari

QuickShop-Hikari turns an ordinary chest into a shop. A player places a chest, fills it with goods, and sets a price — and others can buy. In the same way, you can make a chest that buys instead: it pays money for raw materials.

Shops are of two types. A selling shop means the player sells from their stock and the goods in the chest decrease. A buying shop means the player buys, their goods increase, and the other person pays the money. It is toggled with a command or by clicking the sign by the chest.

A shop is bound to the chest's owner: another player cannot open it, and if the owner breaks it, the shop ceases to exist. Server staff can inspect, move, and remove shops — this is useful when someone places a shop in an inappropriate place.

The number of shops per player is governed by permissions. QuickShop does not add up limits; it maps permissions to a specific number. Everyone has a base (typically 20 shops), and another permission means a higher cap, not an addition to the base. So if you promise an upgrade of thirty shops, the permission must correspond to the target number (50), not thirty — otherwise the player buys something that has no visible effect.

It takes its economy from Vault, so without Vault and an economy plugin, shops do not work. You will only find out when a player tries to buy — so verify it right after installation.

For a server, it is a benefit that trading stays in the game. On public servers, however, it is worth configuring so that shops cannot be created at spawn and in protected areas.

1. Install Vault and an economy plugin — without them QuickShop has no money to draw from.
2. Download QuickShop-Hikari from modrinth.com/plugin/quickshop-hikari for your server version.
3. Upload the .jar to the plugins folder and restart the server.
4. Verify that it is running: /qs help vyp will print help.
5. Open plugins/QuickShop/config.yml and set the basics: default shop type, sign appearance, and whether shops may also be built in protected areas.
6. Set the shop limit according to permissions and verify that the number matches what you promise players (the permission means the target number, not an addition to the base).
7. Assign permissions: a regular player needs quickshop.create.sell and quickshop.create.buy, while management needs quickshop.other.destroy and quickshop.unlimited.
8. Try it yourself: place a chest, put goods in it, and create a shop with the command /qs create .
9. Try buying from yourself on a second account — money must be deducted and goods must decrease from the chest.
10. Try searching: /qs find will list the nearest shops with that item.
11. Set who may remove shops (usually management) so complaints can be handled.

QuickShop does not add up limits, but maps permissions to a specific number of shops. When you promise a thirty-shop upgrade, the permission must correspond to the target number 50 — the difference won't be apparent externally, and the player will find that the purchase brought them nothing.
Without Vault and an economy plugin, shops don't work. Verify this immediately after installation, not only after players start complaining.
Set where shops must not be created — at spawn and in protected areas (WorldGuard, GriefPrevention). Otherwise, the protected town is full of chests with shops.
The sign by the chest is part of the shop: if a player accidentally breaks it, the shop disappears. It's worth explaining this to players.
Sales history (/qs history) is the best tool in a dispute over who bought what. Enable it in the configuration.
When players report that a shop can't be created, check permissions and the shop limit — the plugin message tends to be less specific than one would expect.