Creators
Details
0.2.1-alpha
Compatibility
Changes
Highlights
- Added configurable administrator update notifications, disabled by default.
- Added post-round Play Again and configurable Hub actions.
- Added safe administrator force-start with
/treasurerunadmin forcestart. - Added a shared ranking-query boundary for future ranking features.
Arena ownership and preparation
- Hardened ownership checks for the dedicated
treasurerun_arenaworld. - Existing same-name worlds are no longer treated as TreasureRun-owned by name alone.
- Arena preparation is persisted so the fixed base area does not need to be rebuilt every round.
- Removed large defensive fallback scans from the normal round setup and cleanup path.
Map requirement
No external or DeathRun map is required for this one-arena alpha. TreasureRun creates and uses its own dedicated treasurerun_arena world.
Custom/prebuilt arena maps are not supported by this release and remain part of the later ArenaRegistry / multi-arena work.
Upgrading from v0.2.0-alpha
Before first startup with v0.2.1-alpha on a test server that previously used v0.2.0-alpha:
- Stop the server.
- Back up the server and the existing
treasurerun_arenadirectory. - If that directory is the disposable TreasureRun-generated alpha arena, rename or remove the backed-up directory so v0.2.1-alpha can create a freshly marked arena.
- If ownership of an existing
treasurerun_arenadirectory is uncertain, do not delete it; resolve the name collision first.
Not included yet
/treasurerun top- Optional leaderboard placeholders
- Custom/prebuilt map registration
- ArenaRegistry / multiple arenas
- AutoQueue or timed Auto Mode
- Next-available-arena routing
These remain separate follow-up work.
Special thanks
Thanks to @TymekSL for feedback that informed several of the post-v0.2.0 follow-up improvements in this release.
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:druDRDrE:q3PtwNFS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:druDRDrE:q3PtwNFS"
}

