Minecraft plugin QuickShop-Hikari

🔌 About QuickShop-Hikari

QuickShop-Hikari — is a Minecraft server plugin that allows players and admins to create container-based, in-world shops (chests, barrels, shulkers, etc.) and run a player-driven economy. The plugin is optimized for Paper servers and emphasizes performance and non-blocking (async) operations.

🎯 Purpose

QuickShop-Hikari addresses the need for reliable, container-based shop mechanics where each shop exists as a real block in the world. It targets server administrators who want player-managed marketplaces with lower main-thread overhead. Confirmed scope:

• Container-based shops (chest, barrel, shulker, ...). ()
• Designed for performance / async operations on Paper. ()

⚙ Core features

• Container-based shops that exist as blocks in-game. ()
• Fast, async implementation optimized for Paper. ()
• Flexible pricing and economy features (support for multiple currencies, taxes, discounts) as documented by the project. ()
• Display items (floating item displays above shops) for quick visual identification. ()

🧩 Who it's for

QuickShop-Hikari is suited for:

• Survival and economy-focused servers that want player-run shops.
• Servers running Paper (plugin indicates Paper 1.20+ readiness). ()
• Admins who prefer container-based shop blocks rather than GUI-only store systems.

🏗 Examples of use

• Players create chest shops by interacting with a container and setting prices (container acts as a persistent shop block). ()
• Admins configure server-wide taxes/discounts (feature advertised in docs). ()
• Shops display an item above the container so passersby can see what’s sold. ()

⌨️ Commands

Full command list and arguments are documented in the official QuickShop-Hikari documentation; a complete verified command table was not available in the sources retrieved for this summary. ()

🔐 Permissions

⚙ Installation

📥 Installation

• Download the plugin .jar from an official distribution (Modrinth / Spigot / GitHub releases). ()
• Place the .jar into your server's plugins/ folder.
• Fully restart the server (do not use /reload).

📦 Dependencies

• The project advertises compatibility modules and official addons; no single mandatory dependency was listed on the main page. Official docs list compatibility modules (for example, an OpenInv compatibility module is mentioned that enables /qs echest). Do not assume Vault or others unless explicit in documentation. ()

🧾 Configuration

• The documentation contains a Configuration overview and a Permissions & roles section; exact filenames and DB options were not detailed in the sources accessed for this summary. For detailed config keys, see the project's official docs. ()

🧠 Additional information

• bStats usage: QuickShop-Hikari is listed on bStats (the plugin reports usage statistics unless disabled). ()
• Open source: project and docs are published and link to GitHub / releases from the docs page. ()

⚠ Known conflicts & limitations

• The official documentation recommends checking compatibility modules and addons for integration with third-party plugins; a complete, sourced list of conflicts was not available in the retrieved pages. ()

❓ FAQ

Q1 — Is QuickShop-Hikari open source? A — Yes; the project and its documentation link to GitHub and published releases. ()

Q2 — Does it require Vault? A — No mandatory dependency on Vault is listed on the main site; check the documentation for economy/currency integrations before assuming Vault is required. The docs list compatibility modules instead of a single required dependency. ()

Q3 — Where can I download the plugin? A — Official download/installation sources referenced by the project include Modrinth and Spigot (links available in the documentation). ()

Q4 — Does the plugin collect usage stats? A — The plugin is listed on bStats, indicating that it can report anonymous usage metrics unless disabled. ()

🤝 When to choose QuickShop-Hikari

Choose QuickShop-Hikari if you want container-based, in-world shops with a focus on performance for Paper servers and documented compatibility modules for common integrations. For full command/permission lists and configuration examples, consult the official documentation. ()