Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated 4 months ago
All versions
New
New
2.3.0
Release
EzShops 2.3.07 months ago 123
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
1.7.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
New /pricingadmin command
- Added new
/pricingadmincommand for managing the shop prices- Added
/pricingadmin set <item> <price>subcommand withezshops.pricing.admin.setpermission for setting the price of an item in the shop - Added
/pricingadmin reset <item>subcommand withezshops.pricing.admin.resetpermission for resetting the dynamic pricing of an item in the shop - Added
/pricingadmin resetallsubcommand withezshops.pricing.admin.resetallpermission for resetting all dynamic prices of the shop
- Added
New /shop <category> subcommand
- Added
/shop <category>subcommand to open category GUIs directly - Added missing configurable messages
What's Changed
- Refactor monolithic configuration documentation into sections by @stefkotidis-prog in https://github.com/ez-plugins/EzShops/pull/39
- Shop API builder tools by @ez-plugins in https://github.com/ez-plugins/EzShops/pull/36
- Category gui subcommand by @ez-plugins in https://github.com/ez-plugins/EzShops/pull/42
- docs: add pricingadmin command docs and permissions by @ez-plugins in https://github.com/ez-plugins/EzShops/pull/45
New Contributors
- @stefkotidis-prog made their first contribution in https://github.com/ez-plugins/EzShops/pull/39
Full Changelog: https://github.com/ez-plugins/EzShops/compare/2.2.3...2.3.0
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:zaW55ehx:mxi3qRmS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zaW55ehx:mxi3qRmS"
}

