v2.5.0+mc26.3
Compatibility
Changes
A stable update is available v2.5.0+mc26.3. Check out some improvements:
This new update brings improvements and bug fixes for some important features. One of them involves XP. So, see what has been improved and fixed.
Explanations:
In the beta update, inconsistencies were found in XP calculations not being guaranteed when using the Trade XP Multiplier and Minimum Guaranteed XP. This problem had existed since its implementation due to technical errors.
Causes & Fixes:
- The Trade XP Multiplier and Minimum Guaranteed XP were not working due to a non-functional implementation. The solution was to migrate to a non-destructive approach, allowing the native cycle of version 26.3 to process villager progression without interrupting the game flow.
Implementations:
- Automatic Restock Delay
- Daily Restock Limit
Improvements & Adjustments
- With the XP feature fixes, a visual implementation was added to inject the calculation of the multiplier and the XP floor directly into the visual bar, reflecting the real gain immediately in the client’s visual interface.
- Minimum Guaranteed XP (Floor): Adjusts the base trade value to ensure a minimum reward before the multiplier.
- Trade XP Multiplier (Multiplier): Multiplies the adjusted base, ensuring proportional and predictable XP orbs.
- All XP logic has been wrapped in exception handling (try-catch), preventing crashes and ensuring that the game uses native values as a safety fallback in case of inconsistencies.
Conclusion
Thanks for reading this far. Now everyone can enjoy a consistent and predictable gameplay in this version. Have fun! :)
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:Yf8KPA8u:VnIWMq1T"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Yf8KPA8u:VnIWMq1T"
}

