Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 10 months ago
Updated 47 minutes ago
All versions
0.4.0+mc26.2
Beta
Penchant 0.4.0+mc26.24 months ago 188
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
- Add
#penchant:max_level_enchantmentsitem tag, any item in this tag will receive max level enchantments- Items without durability are intended to be added to this tag, since they cannot level up currently. It will not be the most balanced but at least it is possible now.
- Includes harnesses and horse & nautilus armor by default
- The durability progress cost factor is now controlled by the item component
penchant:enchantment_progress_cost_factor- A fallback value is calculated for each item with durability that does not have the component
- It uses the same formula as before:
clamp(floor(max_durability / 100), 1, 8)
- It uses the same formula as before:
- A fallback value is calculated for each item with durability that does not have the component
- Add experimental module Randomized Librarians
- Librarian villagers will sell an enchanted book that is randomized each time you buy it
- The trades' max uses, cost, and xp are adjusted as follows:
Level Emerald Cost Max Uses Villager XP 1 15 1 6 2 18 1 15 3 20 2 25 4 24 3 45 - Disabled by default
- Fix disabled enchantments appearing in recipe viewers
- Fix enchanting table buttons not respecting API events
- Loot rework: Fix villagers still able to sell some treasure enchantments
- Fix enchanted books with levels higher than 1 appearing in random loot
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| penchant-0.4.0+mc26.2-sources.jar | Sources jar | 229.91 KiB |
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:BTORUTmf:4ZXS3d9I"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BTORUTmf:4ZXS3d9I"
}

