Itemable Bountys
Allows players to place item bounties on other players. When a player with a bounty is killed, the killer receives the bounty items. Includes leaderboards for top targets and top bounty hunters, offline player support, and full customization.
1.1.0
Compatibility
Changes
Itemable Bountys v1.0.2
Database Overhaul
- Migrated storage from YAML to SQLite
- Added HikariCP connection pooling for improved database performance
- New DatabaseManager system for database operations
New Features
- Localization / multi-language support
- Bounty expiration system with configurable timers
- Leaderboard particle effects
- Bounty chest support (Shulker Box rewards)
- Playtime requirement system
- Player settings system
- Item blacklist support
- Item value management
- Advanced notification system
- Detailed bounty logging
Improvements
- Improved global bounty notifications
- New delivery modes (Inventory or Drop)
- New Settings GUI
- Better database caching and configuration options
- More configurable messages and sounds
- Enhanced GUI formatting and usability
- Improved error handling and code quality
Configuration
- Added localization settings
- Added bounty expiration settings
- Added leaderboard particle settings
- Added database configuration options
- Added delivery mode configuration
- Added logging configuration
Technical Changes
- Package renamed from
de.bountyhuntertode.itemable_bountys - Main class renamed to
ItemableBountys - Improved project structure and code organization
Added Dependencies
- SQLite JDBC 3.46.1.3
- HikariCP 5.1.0
- Gson 2.10.1
- JetBrains Annotations 24.1.0
Build Changes
- Added Maven Shade Plugin for shaded/fat JAR builds
Notes
This update modernizes the plugin architecture, improves performance, and introduces multiple new customization options for server owners.
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:Znx9JVdd:xOYwV79u"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Znx9JVdd:xOYwV79u"
}
