1.0-SNAPSHOT
Compatibility
Changes
LuxLifeSteal – Installation & Usage Guide
Installing the Plugin
Follow these steps to install LuxLifeSteal on your Minecraft server.
- Download the
LuxLifeSteal.jarfile. - Place the
.jarfile inside your server'splugins/folder. - Start or restart your Spigot server (API version 1.21).
- Verify the plugin loaded correctly:
- Check the server console for
LuxLifeSteal. - Run
/lifestealin-game.
- Check the server console for
If the folder plugins/LuxLifeSteal/ is created, the plugin has installed successfully.
Commands
| Command | Description | Permission |
|---|---|---|
/lifesteal or /ls |
Opens the admin GUI (players only) | luxlifesteal.admin |
/lifesteal bans |
Opens the banned players menu (players only) | luxlifesteal.admin |
/lifesteal set <player> <amount> |
Sets a player's life count | luxlifesteal.admin |
/lifesteal add <player> <amount> |
Adds lives to a player | luxlifesteal.admin |
/lifesteal remove <player> <amount> |
Removes lives from a player | luxlifesteal.admin |
/lifesteal revive <player> |
Unbans a player and restores starting lives if required | luxlifesteal.admin |
/lifesteal reload |
Reloads plugin configuration files | luxlifesteal.admin |
/hearts |
Shows your own hearts/lives | None |
/hearts <player> |
Shows another player's hearts/lives | luxlifesteal.hearts.others |
Permissions
| Permission | Description | Default |
|---|---|---|
luxlifesteal.admin |
Access to all LuxLifeSteal admin commands and GUI | op |
luxlifesteal.hearts.others |
Allows viewing other players' hearts | op |
Quick Admin Tutorial
Typical workflow for server administrators:
- Give yourself OP or the
luxlifesteal.adminpermission. - Run
/lifestealto open the admin GUI. - Manage player lives using:
/lifesteal set/lifesteal add/lifesteal remove
- If a player reaches zero lives and is banned, run:
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:CvgEizsO:dZcNpjz7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CvgEizsO:dZcNpjz7"
}

