Tags
Creators
Details
2.5.0
Compatibility
Changes
This version we focussed on adding Team Shops, a full team-based economy layer built on top of TeamsAPI. Teams get their own market, shared treasury, stock pool, and role-based pricing, all accessible through a new /teamshop command.

Added
- TeamsAPI integration — EzShops now integrates with TeamsAPI as a soft dependency; all features degrade gracefully when TeamsAPI is absent.
- Role-based sell multipliers — MEMBER, ADMIN and OWNER each receive a configurable sell price bonus when selling to the shop (
teams-integration.sell-multiplierinconfig.yml). - Role-based buy discounts — MEMBER, ADMIN and OWNER each receive a configurable buy price reduction when purchasing from the shop (
teams-integration.buy-discountinconfig.yml). - Team treasury — a shared balance funded automatically by a configurable percentage of every sell transaction (
teams-integration.treasury-split). Members can deposit and withdraw funds through the treasury GUI. - Shared team stock — stock quantities are pooled per team; all members draw from and contribute to the same pool (
teams-integration.shared-stock). /teamshopcommand — opens the team shop dashboard showing team info, current multipliers and quick links./teamshop treasury— opens the team treasury GUI (deposit / withdraw; requiresezshops.teamshop.treasury.withdraw)./teamshop stocks— browse all items your team currently has in stock.
- Permissions:
ezshops.teamshop(default: true) — access the team shop dashboard.ezshops.teamshop.treasury.withdraw(default: true) — withdraw from the team treasury.ezshops.teamshop.admin(default: op) — administrative team stock commands.
- Automatic data cleanup — team stock and treasury data are deleted automatically when a team is disbanded via the
TeamDeleteEvent.
Optional dependencies
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:i781rLFf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zaW55ehx:i781rLFf"
}

