Tags
Creators
Details
Licensed ARR
Published last year
Updated 3 weeks ago
All versions
1.9.0
Release
Lifesteal Plugin 1.9.03 weeks ago 1,713
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
New Heart Tier Progression
The crafting system now supports the complete heart progression:
| Heart tier | Recipe support | Custom ingredient support |
|---|---|---|
| Tier 1 | Existing | Yes |
| Tier 2 | Added | Yes |
| Tier 3 | Added | Yes |
| Tier 4 | Added | Yes |
| Tier 5 | Added | Yes |
Recipe Viewer Improvements
| Change | Description |
|---|---|
Recipe viewer now matches config.yml |
The recipe viewer now reads from the same compiled recipe definitions used by the crafting system. It no longer reconstructs recipes separately from raw materials, eliminating differences between what players see and what Bukkit actually accepts. |
| Correct custom heart icons | Tiered heart ingredients are displayed using cloned custom ItemStack objects containing the correct name, lore, material, persistent item type, and heart-tier value. The viewer no longer displays every heart ingredient as a generic Nether Star or base material. |
| Accurate recipe shapes | Every configured row and ingredient symbol is mapped to the correct slot in the 3×3 recipe preview. Empty characters remain empty, duplicate symbols reuse the correct item, and malformed shapes are rejected before the menu is shown. |
| Accurate result previews | Preview result slots now use the exact item generated by RecipeManager, including configured material, tier value, display name, lore, amount, item flags, and persistent metadata. |
| Live reload refresh | Running /reloadlifesteal or /lifestealadmin reload now rebuilds all currently open recipe-view inventories. Players do not need to close and reopen the menu to see updated shapes, ingredients, results, names, lore, enabled states, or language text. |
| Menu state preservation | During a reload, the viewer preserves the player’s current location in the recipe interface. A player viewing Tier 4 remains on the refreshed Tier 4 preview rather than being forced back to the overview. |
| Animation restart safety | Existing recipe-view animation tasks are cancelled before refreshed menus are installed. New animation state is then created for the rebuilt inventory, preventing duplicate scheduled tasks or stale inventory references. |
| No reload sound spam | Automatically refreshed menus are reopened silently. Normal open, click, and back sounds remain available for direct player navigation, while configuration reloads avoid replaying sounds to every active viewer. |
| Disabled recipe handling | If a recipe is disabled during reload while a player is currently viewing it, the viewer safely returns to an appropriate available menu instead of leaving an invalid or stale preview open. |
| Single recipe data source | Recipe registration, crafting validation, item creation, and GUI previews now share the same normalized recipe catalog. This removes duplicate parsing rules and reduces the chance of future mismatches. |
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:pZ4D6mrk:3DCxxXOL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pZ4D6mrk:3DCxxXOL"
}

