1.2.0
Compatibility
Changes
Item Manager — Version 1.2.0
New: Dimension-based restrictions
Every item can now be restricted globally or only in specific dimensions, including modded dimensions.
- Format:
/itemmanager add banned minecraft:tnt --dim minecraft:the_nether - Works with any dimension using
modid:dimensionformat - Global restrictions (no
--dim) still apply everywhere as before
New: Live config sync — no restart needed
Changes now apply instantly to all connected players.
- Config syncs automatically after every command
- Config syncs to a player when they log in
/itemmanager reloadforces a manual sync to all players
New: /itemmanager reload command
Reloads the config file and syncs it to all online players instantly.
Improved: Custom messages
setmessagecommand now uses|separator for consistency withadd- Color codes using
&now render correctly in tooltips on dedicated servers - Messages can be set per dimension:
/itemmanager add banned minecraft:tnt|&cForbidden! --dim minecraft:the_nether
Bug fixes
- Fixed custom messages not appearing in tooltips on dedicated servers
- Fixed
setmessagerejecting item IDs containing: - Fixed config not updating in memory after being saved
Item Manager — Version 1.0.0
Initial release.
Features included:
- 3 enforcement categories: BANNED, ILLEGAL and RESTRICTED
- BANNED removes items from inventory every second and from containers on open
- ILLEGAL moves items out of hotbar, offhand and armor slots automatically
- RESTRICTED blocks crafting and hides recipes in JEI
- Custom messages per item with
&color code support - Commands with Tab auto-complete
- Requires OP level 2
- Compatible with Forge 1.20.1 and Mohist 1.20.1
- Works with any modded item using
modid:itemnameformat
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:9A1d4Ka8:FrLVth1Y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9A1d4Ka8:FrLVth1Y"
}

