Tags
Creators
Details
All versions
2.0.0+1.21
Release
2.0.0+1.212 years ago 13.5K
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platforms
Fabric
Quilt
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Major update that brings Extended Enchanting into 1.21 Minecraft.
Additions
- Lightning Aspect can apply discharge damage multiple times per tick.
Changes
- Every enchantment has been recreated using the new data-driven system.
- Feint's identifier has been changed:
extended-enchanting:back_foot->extended-enchanting:feint - Lightning Aspect's discharge mechanic has changed to be tick-based.
- Previously:
- Each attack would increase static by 1 or 2 (depending on enchantment level), and the discharge would occur when the counter reaches 5, resetting it. Static would be lost every 25 ticks.
- Now:
- Each attack applies a number of static ticks. 22 per level.
- Static ticks are depleted by 1 every tick.
- If an entity reaches 100 static ticks, it will take discharge damage and lose 100 static ticks.
- This occurs iteratively, an entity with 200 static ticks will be damaged twice in the same tick.
- Previously:
- Due to limitations in the new system, Solitude is no longer incompatible with every other enchantment. It is now incompatible with every treasure enchantment and every non-treasure enchantment.
- In practice this is still every enchantment, but it's controlled by vanilla tags and is therefore technically dependent on other people tagging things correctly.
Removals
- The
additionalDamageEnchantmentPvpEffectivenessgamerule has been removed.- Combat+ Core now offers a
pvpEnchantmentModifiergamerule that performs the same function and is shared with other mods.
- Combat+ Core now offers a
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| extended-enchanting-2.0.0+1.21-sources.jar | Unknown | 247.41 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:pGJRuQZQ:JbRzuK51"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pGJRuQZQ:JbRzuK51"
}

