Tags
Creators
Details
Licensed ARR
Published 6 months ago
Updated 4 months ago
All versions
1.1
Release
SinceEnchantments 1.16 months ago 28
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platform
Paper
Changes
š”ļø SinceEnchantments v1.1 - The Foundation Update
This update introduces a massive refactor of the core systems, improved compatibility with MMOItems, and critical fixes for anvil exploits and visual bugs.
š Key Highlights
| Feature | Description |
|---|---|
| New Items | Added Randomizer Stone, Protection Gem, and Stat Tracker. |
| Modular Config | Config split into enchants.yml, gui.yml, settings.yml, and limits.yml. |
| Vanilla+ Support | Freshly crafted gear now displays slots/whitelists immediately. |
š Full Change Log
⨠New Features & Refactors
- Config Evolution: Moved from a single file to a modular system for better management.
- Smart Categories: Full support for Vanilla wildcards (e.g.,
*_PICKAXE) and MMOItems (Type:ID). - Dynamic Protection: Toggle whether Protection Gems are permanent or consumed on death in
settings.yml.
š”ļø Exploit & Security Fixes
- Anvil Hardening: Enchantment books must now be applied via drag-and-drop (prevents bypassing RNG).
- Fixed bypasses for Max Slots and incompatible enchantments during merging.
- Combat Balance: Lifesteal no longer works on Armor Stands or dead corpses.
- Grief Prevention: Excavator now respects WorldGuard/Towny protection.
š Bug Fixes & UX
- Visual Polish: Fixed
{enchants}placeholder lingering on clean items. - Stat Trackers: Fixed instant rendering (starts at 0) and isolated applicator NBT keys.
- Ghost Items: Resolved the "Ghost Item" cursor bug when using the last Extractor.
- Addon System: Fixed a critical
NoClassDefFoundErrorin the AddonLoader.
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:C8Aqsupg:8HsijMeh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:C8Aqsupg:8HsijMeh"
}

