Links
Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 6 months ago
All versions
1.2.7
Release
Xshards 1.2.77 months ago 526
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
ersion 1.2.7 - Shop GUI Customization (Database Edition)
Features:
- NEW: Customize shop inventory title in config.yml (store.title)
- NEW: Per-item custom display names (editable via /store editname <slot> <name>)
- NEW: Per-item custom lore (editable via /store editlore <slot> <line1|line2|...>)
- NEW: Global default lore for all shop items in config.yml
- NEW: Full color code support (&a, &c, etc.) for all customizations
- Support for {price} placeholder in lore
Database Schema Updates:
- Added
display_namecolumn to shop_items table (VARCHAR 256 / TEXT) - Added
lorecolumn to shop_items table (LONGTEXT / TEXT) - Backward compatible - existing shops auto-migrate
New Commands:
/store editname <slot> <name>- Set custom display name for item/store editlore <slot> <line1|line2|...>- Set lore with | as separator
Configuration Example:
store:
title: "&6Custom Shop Name"
default-lore:
- "&7Price: {price} shards"
- "&8Click to purchase"
Data Storage:
- Per-item customizations saved in database (MySQL/SQLite)
- Global settings configured in config.yml
- Changes via commands immediately persist to database
Technical Updates:
- Updated version to 1.2.7
- Added display_name and lore fields to ShopItem class
- Updated DatabaseManager table creation for both MySQL and SQLite
- Enhanced ShopManager with batch save/load for customizations
- Added setItemDisplayName() and setItemLore() methods
- Tab completion for editname and editlore commands
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:dj6mn5Xl:jNLilOgs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dj6mn5Xl:jNLilOgs"
}

