Tags
Creators
Details
1.4.1-BETA
Compatibility
Changes
📦 ScavengerHunt v1.4-BETA
Build Status: Stable / Feature-Complete / Not Tested Yet
Target API: Minecraft 1.21+
A massive architectural overhaul! Version 1.4-BETA transitions the core game from a hardcoded prototype into a highly flexible, production-ready event manager. This release introduces dynamic reward bridges, automated match safety nets, and full MiniMessage customization.
✨ New Features & Enhancements
🎮 Universal Reward Bridge (Soft Dependencies):
Added seamless API hooks for Vault and PlayerPoints.
Engineered safely as Soft Dependencies—if Vault or PlayerPoints are missing, the plugin dynamically disables those reward pathways on startup instead of crashing.
Added a Custom Console Commands executor (%player% placeholder supported), enabling compatibility with custom item/crate key plugins.
⏱️ Anti-Softlock Auto End:
Introduced a configurable time-limit (in seconds) to prevent matches from running indefinitely.
If no player discovers their targeted item before the timer expires, the hunt automatically ends gracefully and safely clears all active scoreboards.
🎨 Dedicated Localization (messages.yml):
Decoupled chat components from the core code into a dedicated, isolated translation file.
Fully integrated the MiniMessage Parser Engine, allowing for advanced text formatting, hex gradients, and responsive typography.
📊 Dynamic Placeholder Integration:
The gameplay elements now actively parse native placeholders like <item>, <player>, and <time> straight out of your custom configuration strings.
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:ofeDU2xo:YmZARVwh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ofeDU2xo:YmZARVwh"
}

