Tags
Creators
Details
Licensed ARR
Published 6 months ago
Updated 5 months ago
All versions
1.3
Release
Claim system, Autoclaim on join, reminders, new PAPI support6 months ago 20
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
ItemCoreX 1.3
This update adds a much safer item delivery system for custom items and improves ItemCoreX integration with PlaceholderAPI and third-party plugins.
New
- Added a persistent pending / claim system for custom items
- Added
/ic claimfor players to claim saved pending items - Added SQLite-based storage for pending items
- Added auto-claim on join
- Added join reminder if pending items still exist
- Added new PlaceholderAPI placeholders:
%itemcorex_pending_total%%itemcorex_has_pending%%itemcorex_pending_<key>%
Improved
- Improved custom item delivery when player inventories are full
- Custom items are now partially delivered if possible, while the rest is saved safely
- Claiming pending items now also supports partial delivery if the inventory is still too full
- Improved safety against item loss and duplicate issues in claim handling
- Improved TabCompleter behavior:
- players now only see
/ic claim - admin commands stay hidden from normal users
- players now only see
- Improved PlaceholderAPI support for menu, NPC, UI and reward setups
Config
New claim settings in config.yml:
claim:
auto-claim-on-join: true
reminder-on-join: true
This update is especially useful for servers using:
DeluxeMenus
FancyNPCs
mob reward systems
PlaceholderAPI-based menus and UI
servers with custom item drops and full-inventory situations
ItemCoreX 1.3 focuses heavily on safer custom item handling in real server environments.
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:aC54VC4N:8dscFL9Q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aC54VC4N:8dscFL9Q"
}

