Tags
Creators
Details
1.5
Compatibility
Changes
SmartInventory 1.5 — Secure Access Update
SmartInventory 1.5 brings a new access system, better compatibility, persistent settings, and many internal improvements.
New access system
SmartInventory now uses deny-by-default access. New players cannot use its features until an administrator gives them permission.
You can manage individual players with:
/smartinv admin <player> on
/smartinv admin <player> off
/smartinv admin <player> status
You can also manage the built-in access group:
/smartinv admin group add <players...>
/smartinv admin group remove <players...>
/smartinv admin group list
Optional LuckPerms permissions were also added:
smartinventory.use
smartinventory.smartinv
smartinventory.smartchest
smartinventory.admin
Improvements
- Player preferences are now saved in
player-settings.yml. - Settings are preserved after reconnecting or restarting the server.
/smartinv on|off|statusnow controls both inventories and containers.- All commands are now unified under
/smartinv. - Missing language keys are added automatically without replacing custom messages.
- Added complete translations for 10 languages.
- Improved command suggestions and language messages.
- Added automatic validation for
plugin.ymland language files.
Fixes
- Fixed unauthorized players being able to use the plugin.
- Fixed new players starting with features enabled.
- Fixed preferences being lost after restarts.
- Fixed Folia scheduler and shared-data issues.
- Fixed malformed
plugin.ymlfiles. - Fixed missing and incomplete translations.
Removed
The following commands were removed:
/smartchest
/smartinventoryadmin
/siadmin
Their functionality is now available through /smartinv.
Updating
Stop the server, replace the old JAR, and start it normally. Do not use /reload.
Existing players must now be authorized through /smartinv admin, the internal group, or a permission plugin.
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:nSYXpKTb:fwNVghOJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nSYXpKTb:fwNVghOJ"
}

