1.0.0
Compatibility
Changes
⨠Overview AnvilCap enhances the vanilla anvil system by removing the frustrating "Too Expensive" limitation, allowing players to freely repair, combine, and upgrade items without artificial restrictions.
âď¸ Core Features
- Removed the vanilla "Too Expensive" limit from anvils
- Allows high-level item repairs and enchant combinations
- Enables late-game progression without unnecessary restrictions
đ§ Anvil Mechanics Improvements
- Overrides the default maximum repair cost
- Ensures items remain craftable even when exceeding vanilla limits
- Prevents the anvil result from disappearing due to high XP cost
- Maintains vanilla behavior while removing limitations
âď¸ Configuration System
- Added configurable maximum XP cost
- Default max XP cost set to 37 levels
- Server owners can fully customize the anvil cap to fit their gameplay balance
- Automatically generates a config file on first startup
Example: max-xp-cost: 37
đ§ Performance & Optimization
- Lightweight implementation with minimal performance impact
- Uses event-based logic (PrepareAnvilEvent) for efficiency
- No unnecessary tasks or background processes
đ ď¸ Compatibility
- Designed for Paper 1.21+
- Works with Spigot-based servers (not officially tested)
- Compatible with vanilla mechanics and most plugins
đ Bug Fixes
- Fixed issue where anvil result would not appear when exceeding cost limit
- Fixed XP cost not being applied correctly
- Fixed inconsistencies with anvil behavior at high levels
đ Use Cases
- Ideal for survival servers with long-term progression
- Perfect for RPG-style servers with high-level enchantments
- Useful for servers that want to remove frustrating vanilla limits
đŽ Future Plans
- Bug Fixes
- New Configurable Anvil System
đ¤ Author Developed by uuirco
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:ejBKCB9X:BXzEz0qr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ejBKCB9X:BXzEz0qr"
}

