Tags
Creators
Details
1.0-Alpha.1
Compatibility
Changes
š LifeStealX v1.0-Alpha.1
This update focuses on polishing, stability, and quality of life improvements based on early Alpha feedback.
⨠New Features
-
š Added
/ls recipewith a visual recipe preview GUI. -
ā¹ļø Added
/ls infowith plugin information and configurable links. -
āļø Added a configurable combat ActionBar timer.
-
š Added elimination announcements with titles, sounds and particle effects.
-
⨠Added revive particle effects.
-
š¾ Added automatic player data saving every 5 minutes.
-
āļø Crafting recipes are now fully configurable through
config.yml. -
š Added configurable website, GitHub and Discord links.
š§ Improvements
-
Combat start sound now only plays when entering combat.
-
Improved combat logging behavior.
-
Improved Revive Beacon reliability.
-
Better command help with gradients and permission-aware command visibility.
-
Completely redesigned and documented configuration file.
-
Improved recipe management system.
-
Better shutdown handling and autosave protection.
š Bug Fixes
-
Fixed an issue where hearts could incorrectly be withdrawn at the minimum heart limit.
-
Fixed unsafe recipe configuration loading.
-
Fixed multiple revive edge cases.
-
Fixed duplicate revive prevention.
-
Fixed several combat edge cases.
-
Fixed inventory handling after revive.
-
Various code cleanup and internal stability improvements.
ā” Performance & Internal
-
Improved thread safety.
-
Improved configuration validation.
-
Better error handling.
-
Cleaner internal architecture.
-
No deprecated API usage.
-
Zero compiler warnings.
-
Build verified successfully.
ā ļø Alpha Notice
LifeStealX is still in Alpha.
While the plugin is already fully playable, some features may still receive improvements and additional polishing. Feedback and bug reports are greatly appreciated!
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:JFNwCck8:IJbQXdqQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JFNwCck8:IJbQXdqQ"
}

