Tags
Creators
Details
2.5.6
Compatibility
Changes
Through time we've made the stock market more stable, by doing this the documentation got outdated and configuration options that existed before got phased out. This version there was focus on updating the documentation and adding back options that got phased out in a more stable way.
Added
- Configurable stock price-engine parameters -
volatility-min,volatility-max,demand-multiplier,min-price, andupdate-intervalare now realconfig.ymloptions under thestock:section. The plugin reads them on startup and applies them to the price engine. All defaults match the previously hardcoded values so existing behaviour is preserved.
Fixed
- Incorrect stock-market configuration documented -
docs/configuration/main-settings.mdanddocs/shops/pricing/stock-market.mdpreviously documented a non-existentstock-market:config block. Both pages now document the realstock:section (enabled,cooldown-millis,blocked,overrides,categories). Price-engine parameters (volatility-min,volatility-max,demand-multiplier,min-price,update-interval) are now implemented as real config options (see Unreleased → Added). /sellcommand missing from documentation - the Quick Sell GUI command (/sell) is now documented in the Commands reference with its behavior and permission node./shopadmincommand missing from documentation -/shopadmin [browse|market]is now documented under Admin Commands including both the player-shops and team-market views./teamshop marketsubcommand missing from documentation - the team P2P market subcommand is now documented in Commands, the TeamsAPI integration page, and the tab-completion list for/teamshop.- Missing permission nodes in documentation - the following nodes were present in
plugin.ymlbut absent from the Permissions reference; they are now documented:ezshops.shop.admin(open/shopadminGUI)ezshops.teamshop.market(access team P2P market)ezshops.pricing.admin.set,ezshops.pricing.admin.disable,ezshops.pricing.admin.list(granular pricing-admin nodes)
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:8LZOXLbb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zaW55ehx:8LZOXLbb"
}

