3.2.0
Compatibility
Changes
๐ ItemCap 3.2.0 โ Performance, Customization & More
This update focuses on performance improvements, greater customization, and more admin configs.
๐ What's New
๐ ๏ธ New Features
- Added the
/ic tag <player> <item> <amount>command to manually tag limited items(permission:ItemCap.tag). - Added an Admin Configuration for manually tagging limited items.
- Added a System Enabled option in the configuration, allowing you to completely enable or disable ItemCap for reduced resource usage when it's not needed.
๐ง Improvements
- โก Significantly optimized the plugin for better performance.
- ๐งน Removed unused and legacy code.
- ๐ฆ Cleaned up and compacted the codebase for easier maintenance.
- ๐ Fixed multiple bugs and improved overall stability.
๐ Help & Support
Need help, found a bug, or have a suggestion?
๐ Join our Discord to watch the support/setup video, report issues, and get help from the community.
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:GLEetOKp:A9pN4igL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GLEetOKp:A9pN4igL"
}

