Tags
Creators
Details
1.5
Compatibility
Changes

Added new permission nodes ki.onjoin.on and ki.onjoin.off
If the player joins the server and has either one of the permission nodes mentioned above, it'll automatically have KeepInventory enabled or disabled.
Blacklisted worlds will still prevent the player from having KeepInventory enabled.
Added new config option debug.send-on-join-notification
By default, this config option is set to "false", but if enabled, it'll send the joining player a message about KeepInventory being enabled or disabled for them.
Added three new messages for the on-join notifications
Now introducing: KeepInvAPI
You can now use KeepInventory Individual inside your project's library! Right now, it only lets you enable and disable KeepInventory for the specified player. More info on the wiki!
As always, please don't hesitate reaching out to me, if you got any questions or if something is not working right.
And remember, please do not use the review section to seek support.
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:1QZbMb72:ssibFkwj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1QZbMb72:ssibFkwj"
}

