Tags
Creators
Details
Licensed ARR
Published 11 months ago
Updated 5 months ago
All versions
0.1.5-neoforge-1.21.10
Beta
Dynamic Enchants 0.1.5-neoforge-1.21.109 months ago 32
Compatibility
Minecraft: Java Edition
1.21.10
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog - Dynamic Enchants
Beta Release: Armor Slots & Repair Core Update
New Features
- Universal Armor Wing: Added 4 vertical equipment slots to the left side of the Enchant and Anvil pages. These slots are linked directly to your player's actual worn armor for quick access.
- Anvil Repair Core: Added the
REPAIR_CORE. You can now place this in the repair-book slot to handle all items (Tools, Weapons, and Armor) without having to swap books out all the time. It works at a fixed slower speed, so specialized high-level books are still the best option for fast repairs.
Fixes & Improvements
- Visual Stack Display: High-capacity items in the Collector grid now show their true counts (96, 128, etc.) in Yellow text.
- Filter Persistence: The Fuzzy and Blacklist/Whitelist settings now correctly save to the block and survive world reloads or chunk unloads.
- GUI Focus Fix: Fixed the bug where the Anvil and XP Bank text boxes wouldn't "let go" of the focus. ESC now correctly stops typing without closing the whole menu.
- XP Bar Tooltip:
- Fixed the math to center the tooltip perfectly.
- Holding Shift now shows the current stored amount vs the total tank capacity.
- Quick Move (Collector): You can now shift-click items out of the Collector buffer from any page (Page 2, 3, 4, etc.).
- Magnet Book Swapping: Updated the rules to allow swapping books on any page if your items fit, while still protecting your buffer items from being lost.
- Slot Security: Globally blocked the 'F' key (off-hand swap) while the Lectern is open to prevent players from bypassing slot rules.
- Filter Wing:
- The wing now automatically closes when you exit the GUI.
- Additionally, the page buttons (
<and>) are now hidden and disabled while the wing is expanded to prevent them from being blocked by the panel.
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:QAKIT0XP:x0rzo2pp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QAKIT0XP:x0rzo2pp"
}

