Tags
Creators
Details
Licensed ARR
Published last year
Updated 23 hours ago
All versions
Spigot_Paper_Purpur_Folia_1.1.0
Release
ShopShelves 1.1.0yesterday 15
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.9–1.21.11
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
A big quality update: languages, new integrations, an optional purchase confirmation and many fixes.
New
- Languages: new "language" setting in config.yml. Translations live in the plugin's lang/ folder (e.g. lang/fr.yml). When you switch to a language that has a translation, your messages.yml is renamed to messages_en_us.yml and messages_fr.yml is created next to it. Every language keeps its own file with your edits, and switching back uses it again. Languages without a translation fall back to English.
- New help page: /shops now shows a survival-friendly guide that explains how to create, stock, price and manage a player shop, with hover tips on every line. Admins get a clickable button to the admin command overview (/shops help admin).
- Purchase confirmation (optional): confirm_transactions: true makes every buy and sell need a second click within confirm_timeout_seconds. The first click shows what you are about to buy or sell and for how much.
- Claim plugins: player shops inside a GriefPrevention claim, Towny town block or Lands chunk are removed when that claim is deleted, abandoned, expires or is unclaimed (delete_shops_on_claim_removal). Admin shops are never removed.
- Web maps: shops show up as markers on BlueMap, Dynmap and squaremap, with the owner, label and items for sale. Player and admin shops can be toggled separately in the new web_map section.
Fixed
- Double chests: Existing single chest shops had double chest non protection.
- SELL-only shops now answer with "not for sale" when someone tries to buy.
- Right-clicking an already empty slot with an empty hand no longer says the slot was cleared.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:SmwrUlZx:z8t5yqGn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SmwrUlZx:z8t5yqGn"
}

