All versions
1.0.2
Release
Refresh Trades 1.0.28 months ago 310
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Forge
Supported environments
Client and server
Changes
- Fixed cooldown logic so it is tracked per specific merchant instead of globally per player.
- Fixed offer generation so invalid entries no longer reduce the final reroll result.
- Fixed emerald payment checks so emeralds in merchant payment slots and the carried stack are counted correctly.
- Split reroll handling into dedicated validation, state and offer services.
- Replaced fragile reflective merchant access with an access transformer based path.
- Added button state sync from server to client.
- Added loading, cooldown and paid-refresh button states with localized tooltips.
- Reset selected trade after reroll and synchronized the refreshed merchant state back to the screen.
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:tcR4gZGe:8sFFZN2E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tcR4gZGe:8sFFZN2E"
}

