All versions
3.0.0
Release
BountyLoss 3.0.0 SERVER SIDE ONLY2 months ago 51
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Server-side
Client and server
Changes
Server-Side Only :
- Bounty Loss no longer requires players to install anything client-side — the mod now runs entirely on the server.
- All custom items (Heart, Revival Beacon, and the 6 relics) are now reskinned vanilla items instead of registered custom items, so a completely vanilla client can join and play with zero setup.
- Added an optional companion resource pack for players who want the items to actually look like Hearts/Relics instead of their vanilla base item (Golden Apple, Totem of Undying, etc.) — purely cosmetic, safe to skip.
Bounty Loss Toggle :
- The mod no longer starts assigning bounties automatically — admins now control exactly when the season begins with /bountyloss start.
- Added /bountyloss stop to end the current run at any time. This clears all active bounties, cooldowns, and the current Most Wanted player, so the next /bountyloss start begins a clean slate.
- Until /bountyloss start is run, players can join and play normally without being assigned a target.
New Admin Commands :
- /bountyitems – gives you one of every bounty item, for testing/admin purposes.
- /bountyitems <item> [count] – gives you a specific bounty item (Heart, Revival Beacon, or any relic), with tab-completion for valid item names.
- /bounty reroll <player> – forces a player's current bounty target to be replaced with a brand new random one, bypassing cooldown.
Easy commands :
- Every command that takes a player's name (/revive, /sethearts, /skipbountycooldown, /setbounty) now tab-completes with the names of currently online players.
- Fixed the relics being different sizes and not centered with the new resource pack .
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:hNMOtriZ:X85nPSW8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hNMOtriZ:X85nPSW8"
}

