2.0.0
Compatibility
Required content
Changes
Thorium Lifesteal Update
This update adds major Lifesteal event features, team base claiming, craftable hearts, and better server-side protections.
Important Updates
Team Base Claims
Players can now claim a team base using:
/base claim
- Base claiming is player/team controlled
- A claimed base covers a 2x2 chunk area.
- Base claims are saved and survive server restarts.
- Coordinates are only shown privately to the player/team through
/base info.
Locator Bar Base Protection
Inside a claimed team base, players are hidden from the locator bar only.
Important notes:
- Carved Pumpkins and Invisibility Potions do not hide players from the locator bar outside claimed bases.
Craftable Hearts
Thorium Hearts are now craftable.
Recipe:

Right-click a crafted heart to gain +1 Lifesteal heart.
The recipe is built into the mod jar. A separate datapack zip is also included for server owners who want it.
Heart Withdraw Command
Added:
/withdraw
/withdraw <amount>
Players can withdraw real hearts into Thorium Heart items.
Rules:
- Players must keep at least 1 heart.
- Withdrawn hearts become usable heart items.
- Heart items respect the server heart cap.
Simple Voice Chat Team Groups
Team voice groups are automatically created for each team.
- Team 1 through Team 5 groups are supported.
- Players are automatically moved into their own team voice group.
- Players cannot join another team’s voice group.
- Admins can still manage/monitor as needed.
Restart-Safe Data
The mod now saves important event data permanently, including:
- Player hearts
- Eliminations
- Teams
- Base claims
- Final event state
- Grace period state
- Mace state
This makes the mod safer for real events and
Optional dependencies
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:9byQAcKL:3KAMiu4y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9byQAcKL:3KAMiu4y"
}
