All versions
1.1
Release
LivesPlugin 1.1last year 299
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
π Changelog β v1.1
β¨ New Additions
- Added
messages.ymlβ all plugin messages are now stored separately for easy editing and customization. - Implemented dynamic reloading for both
config.ymlandmessages.ymlusing/livesreload. - Enhanced recipe editor functionality and stability.
- Improved TAB display handling with real-time updates when reloading the plugin.
βοΈ Improvements
- Renamed
/recipeβ/livesrecipeto avoid command conflicts. - Removed
/helpcommand to prevent interference with other plugins β use/livesplugin helpinstead. - βReset to Defaultβ in the recipe editor now auto-saves, closes the menu, and confirms via message.
- Recipe validation system improved to prevent shape and symbol errors.
- Updated default Revive Book recipe for better material balance and progression.
- TAB display now respects the
enabledoption in the config. - Disabled the ability to craft a beacon with the LifeStar.
π§ Bug Fixes
- Fixed startup crash caused by invalid recipe symbols.
- Fixed reset to default requiring a second save to take effect.
- Fixed
livesplugin:recipeincorrectly showing the help menu instead of opening the editor. - Fixed messages.yml not saving or reloading properly.
- Fixed tab display toggle not disabling when set to false.
π Misc
- Messages are now entirely configurable in
messages.ymlβ no more message editing inconfig.yml. - Overall plugin stability, reload performance, and error handling improved.
- Made with β€οΈ by Kai
- Support & community on Discord: https://discord.gg/Ha3FHZBX5Q
- Licensed under All Rights Reserved (ARR)
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:fSPFaZbf:NIbVGbLt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fSPFaZbf:NIbVGbLt"
}

