Tags
Creators
Details
Licensed ARR
Published 11 months ago
Updated 5 months ago
All versions
0.1.4-neoforge-1.21.10
Beta
Dynamic Enchants 0.1.4-neoforge-1.21.109 months ago 23
Compatibility
Minecraft: Java Edition
1.21.10
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog - Dynamic Enchants
Beta Implementation: Item Vacuum & Collector (In-Progress)
Lectern of Wisdom Addon: Collector Tab
- Item Collection: Added the Magnet Book slot to the XP Bank tab to activate the Item Vacuum.
- Smart Vacuum: Suctions nearby items within range (2-12 blocks) into a new dedicated storage buffer.
- Storage Buffer: Implemented a high-capacity 144-slot buffer with tiered stack limits based on Magnet level (up to 324+ items per slot).
- Advanced Filtering: Added a collapsible 4x2 Filter Wing with Whitelist/Blacklist modes and Fuzzy Matching (Item Type only) support.
- Safety & Security:
- Implemented "Removal Lock": Magnet book cannot be removed if the buffer contains items. Upgrades are allowed while items are present, but downgrades or full removal require empty storage.
- Refined shift-clicking rules to prevent item loss in hidden grids.
- Technical Stability:
- Fixed high-capacity item serialization issues.
- Resolved item duplication on world rejoin.
- Fixed missing spawn egg trades on dedicated servers via network synchronization.
General Improvements
- UX Polish: Changed all cost/refund readouts to "Lvl" (Experience Levels) for better readability.
- XP Bar Tooltip: Hovering over the XP bar now shows precise progress (Current / Next Level).
- Anvil Correction: Fixed repair material consumption amounts.
Known Issues (Beta)
- Visual Stack Limit: Items in the Collector buffer visually cap at "64" in the slot grid. The correct real count is shown when the item is picked up.
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:UPNIUK1B"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QAKIT0XP:UPNIUK1B"
}

