All versions
1.1
Release
Enchanted Edge3 weeks ago 18
Compatibility
Minecraft: Java Edition
1.20.1โ1.20.6
Platform
Forge
Supported environments
Client and server
Required content
Changes
๐ Enchanted Edge Changelog - Version 1.1
Here are the new features and changes introduced in this version:
โจ New Enchantments
- Ultra Exp (I-III): Experience multiplier (+15%, +30%, +50%) for mining and killing mobs.
- Repulsor (I-II): 20% or 40% chance to knock back attackers when you take damage.
- Frost Arrow (I-II): Arrows apply Slowness and Mining Fatigue to the target (8-second cooldown).
- Last Stand: Gain Strength II and Speed II for 10 seconds if your health drops below 20% (60-second cooldown).
๐ ๏ธ Configuration System (GUI)
- Cloth Config Integration: The "Config" button in the mod list is now active.
- Full Control: You can individually enable or disable any enchantment via a simple visual interface (On/Off).
- Organized Categories: Settings are grouped into Mining, Combat, Utility, and Curses.
๐ง Improvements & Fixes
- Anvil Fix: Removed the "Too Expensive" limit. You can now repair and combine items regardless of the level cost.
- Tooltip Filtering: Detailed enchantment descriptions now appear only on books (Enchanted Books), keeping tool and armor tooltips clean.
- Bulldozer Logic: AOE mining modes have been calibrated (Level 1: 3x1, Level 2: 3x3, Level 3: 3x3x3).
- Magnetize: Item attraction radius is set to a balanced 4 blocks per level.
- Collector: Spawn Egg drop chance is fixed at 4%.
๐งน Code Maintenance
- Clean Architecture: All comments and redundant code have been removed for better performance.
- Localization: All new strings have been added to
en_us.jsonfor full translation support.
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:rrQ9UiBK:CMNbjHJu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rrQ9UiBK:CMNbjHJu"
}


