
Open Inventory
OpenInv is a powerful Minecraft admin plugin that lets staff view and edit player inventories and ender chests using /inv commands, featuring a modern GUI, database-backed inventory snapshots, rollback support, and multiple Minecraft version support.
Tags
Creators
Details
1.3
Compatibility
Changes
β¨ OpenInv v1.3 - Changelog
π Different Worlds, Different Items
The plugin now perfectly supports servers with multiple worlds!
- Per-World Saving: If a player has different items in your "Survival" world and your "Creative" world, the plugin now remembers them separately.
- Auto-Save on Teleport: Whenever a player moves from one world to another, the plugin instantly saves their items so you always see the most recent data.
- Smart Editing: If you edit a player's inventory for a world they aren't currently in, the changes will "wait" for them and apply automatically the next time they enter that world.
π οΈ Smarter Commands
Weβve made the commands much easier to use:
- Unified
/inv: You can now use/inv <player> [world]to check anyone. If they are online, it shows their live items. If you want to check a specific world they aren't in, it automatically shows you their saved items for that world.
β¨οΈ Faster Typing (Tab-Complete)
Typing commands is now much faster:
- Online vs. Offline: When you type
/inv, it will only suggest players who are actually online. When you type/offlineinv, it will only suggest players who are offline. This keeps your list clean! - World Suggestions: When you are typing an inventory command, you can now press
TABto see a list of all your server's worlds (likeworld,world_nether, etc.) so you don't have to remember the exact names.
π Other Improvements
- More Reliable: We fixed several small bugs to make sure player items are always saved safely and never get mixed up between worlds.
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:CJ1sB5q4:SnZmqhuK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CJ1sB5q4:SnZmqhuK"
}
