1.0.3
Compatibility
Changes
PvPRandom v1.0.3 - Treasure Hunt Update
This update introduces an exciting new game mode - Treasure Hunt - along with several improvements and fixes to enhance your PvP experience!
โจ New Features
Treasure Hunt Game Mode - A brand new competitive mode where players:
Search for diamonds hidden in barrels across a floating glass arena
Compete to collect the most treasures (2 diamonds = 1 treasure)
Watch the scoreboard to track progress
Platform collapses shortly after the game begins
Last player standing with the required treasures wins!
New Command:
/pvprandom treasurehunt <kit> <size> <treasures> <goal> <players> - Start a treasure hunt game
kit: Choose from all available kits (random, crystal, classic, etc.)
size: Arena size (50-500 blocks)
treasures: Number of treasure barrels to spawn (10-500)
goal: Treasures needed to win (1-100)
players: List of participating players
๐ ๏ธ Improvements
Scoreboard System:
New treasure tracking scoreboard that updates in real-time
Shows each player's collected treasure count
Automatically displays when treasure hunt starts
Game Mechanics:
Improved glass platform generation for treasure hunt
Better barrel placement algorithm with random diamond amounts (1-8 per barrel)
Automatic teleportation to spawn when game ends
Winner announcement with special effects
๐ Bug Fixes
Fixed potential memory leaks with game timers
Improved scoreboard objective handling
Fixed edge cases in diamond counting logic
Resolved issue with platform destruction timing
๐ Technical Changes
Added new treasure hunt game state tracking system
Implemented UUID-based player tracking
Optimized barrel spawning algorithm
Improved world border handling for all game modes
Ready to hunt? Update to PvPRandom v1.0.3 and try the new Treasure Hunt mode today!
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:RykLxGVV:JfqtDstt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RykLxGVV:JfqtDstt"
}

