All versions
3.0.1
Beta
KeepInventoryShop v3.0.19 months ago 19
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Spigot
Changes
KeepInventoryShop v3.0.1 Changelog
Bug Fixes
End Void Death Fix
- Fixed: KeepTotem now properly respects real Totems of Undying in The End
- If you have a real totem in your main hand or offhand, it will activate first (vanilla behavior)
- KeepTotem lives are only consumed when no real totem is present
- Fixed: Double life consumption when dying to void damage in The End
- Previously, falling into the void could consume both a KeepTotem life AND a normal life
- Now only one life is consumed per death as intended
- Fixed: Gamerule detection - if
keepInventorygamerule is set totrue, the plugin will not consume any lives (vanilla already handles it)
New Features
Custom Messages (messages.yml)
- All player-facing messages are now fully customizable via
messages.yml - Supports color codes using
&(e.g.,&afor green,&cfor red,&dfor light purple) - Placeholder support for dynamic values:
{amount}- number of lives{lives}- "life" or "lives" (grammatically correct){player}- player name{cost}- formatted cost{balance}- player's balance{limit}- life limit{time}- formatted time{remaining}- remaining lives
- Use
/ki reloadto reload messages without restarting the server
Config Comments Preserved
- Comments in
config.ymlare now preserved when the server starts - Previously, all comments were stripped on first load
bStats Integration
- Added bStats metrics for anonymous usage statistics
- View stats at: https://bstats.org/plugin/bukkit/KeepInventoryShop/29348
Technical Changes
- Added
EntityResurrectEventlistener to detect vanilla totem activation - Added real totem detection before consuming KeepTotem lives
- Added double-consumption prevention using UUID tracking
- Switched from
copyDefaults()tosaveResource()for config loading - Added
reloadPluginConfig()method for hot-reloading both configs
Full Compatibility: Minecraft 1.21.0 - 1.21.11
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:FaUbpMea:51oT49Qd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FaUbpMea:51oT49Qd"
}

