Tags
Creators
Details
1.8.1
Compatibility
Changes
New in this release
- š Anvil-made enchanted books now count for inventory challenges ā items that pass through an anvil (for example two enchanted books combined into a higher level) carry a
repair_costcomponent, and the strict item comparison treated them as a different item. Challenges could only be completed by enabling "ignore metadata", which then accepted any enchanted book. The repair cost is now disregarded when matching required items; enchantments, levels, names, lore and all other item data are still compared. [PR #434] Fixes #433 - š” Traditional Chinese (zh-TW) translation improved and brought to full coverage for the 1.8.0 strings, thanks to @qwe664. [PR #427] [PR #429]
- Build and test tooling: the Plugwright end-to-end suite now builds the Challenges jar itself and requires Java 21+, the Maven wrapper is pinned and verified, and CI publishing pins are updated. No runtime effect. [PR #430] [PR #431] [PR #426]
Compatibility
āļø BentoBox 3.14.0 āļø Minecraft 1.21.x āļø Java 21
Upgrading
- Take backups of your server, for safety
- Download this jar and put it in your addons folder - delete the old one
- Restart the server
š” Locale note: no locale keys were added or renamed. Only the bundled
zh-TW.ymlchanged. If you run a customisedzh-TW.yml, delete it (or merge by hand) to pick up the improved translation. Other languages are unaffected.
Legend
- š” locale files may need to be regenerated or updated.
What's Changed
- fix: ignore anvil repair cost when matching required inventory items by @tastybento in https://github.com/BentoBoxWorld/Challenges/pull/434
- š” Update zh-TW.yml: complete translation coverage for v1.8.0 by @qwe664 in https://github.com/BentoBoxWorld/Challenges/pull/429
- š” Improve Traditional Chinese (zh-TW) translation by @qwe664 in https://github.com/BentoBoxWorld/Challenges/pull/427
- Automate Challenges jar compilation for Plugwright E2E tests and enforce Java 21 by @Drownek in https://github.com/BentoBoxWorld/Challenges/pull/430
- Bump js-yaml from 4.3.0 to 4.3.1 in /e2e/src/test/e2e by @dependabot in https://github.com/BentoBoxWorld/Challenges/pull/431
- ci: bump publish-platforms pin to the multipart-JSON fix by @tastybento in https://github.com/BentoBoxWorld/Challenges/pull/426
Full Changelog: https://github.com/BentoBoxWorld/Challenges/compare/1.8.0...1.8.1
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:XtkUkQ7A:7HmWR8Tz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XtkUkQ7A:7HmWR8Tz"
}

