Links
Tags
Creators
Details
1.2.4
Compatibility
Changes
1.2.4
Added
- Tournaments survive restarts and crashes - Running tournaments pick up where they left off after a restart or crash, with the same participants, scores and end time. Nothing is announced again and entry fees aren't charged again. If a tournament's end time passed while the server was down, it ends right after startup and pays out as usual. Scores are saved every 30 seconds, so a hard crash loses at most the last 30 seconds.
- New
resume-grace-hoursoption (default24): a tournament that ended longer ago than this is closed without rewards instead.
- New
- Weekly & monthly leaderboards - Rank players by points or wins earned since the last reset, next to the all-time leaderboard (which is never reset). Weekly resets Monday 00:00 and monthly on the 1st; both can be changed under
leaderboard-periods. At each reset the top 3 are rewarded and announced.reward-metric: POINTS | WINSdecides which ranking picks the top 3. /dt leaderboard rewards <weekly|monthly>- Set up weekly/monthly rewards (commands and items) in the same GUI as tournament rewards -dtournaments.admin.rewards- Leaderboard holograms -
dtournaments.admin.rewards/dt leaderboard hologram paste <weekly|monthly> [name]/dt leaderboard hologram remove <name>/dt leaderboard hologram list- Shows the top 3 plus each viewer's own rank. Click it to flip to a second page, for example to list the rewards.
- The layout lives in
hologram-templates/, and edits apply to every pasted hologram. - Built in, no hologram plugin needed.
- Leaderboard GUI can now switch between All-Time, Weekly and Monthly
- New placeholders
%dtournaments_active_id%- the active tournament's ID (its file name, e.g.mine_diamond_ore), handy for conditions%dtournaments_active_description%- the active tournament's description, e.g. for menu item lore
- Vanish support -
ignore-vanished-players(on by default). Works with any vanish plugin that sets the standard "vanished" metadata (dVanish (yet to be released), PremiumVanish, SuperVanish, Essentials, CMI, ...). Vanished players aren't auto-enrolled, don't count towards min-players, and their score is frozen. Reappearing counts as joining./dt forcejoin <id> allskips vanished players; force-joining one by name still works. - Built-in anti-farm replaces the CoreProtect integration - Still stops players scoring by placing and re-breaking the same block, but no longer needs CoreProtect or a database lookup on every block break. It now covers
block_placetoo.- Settings:
anti-farm.enabled,window-seconds,max-tracked-blocks - Per tournament:
anti-farm.enabled
- Settings:
- New config options and messages are added to your existing
config.ymland translation files automatically on startup and/dt reload
Changed
- Only players who actually scored can place. A tournament where nobody scored now ends with no winner and pays no rewards, with a new "nobody scored" message. A player with 0 points can no longer take 2nd/3rd place behind real scorers. Everyone still gets a participation in their stats.
- worlds-blacklist edits now apply to running tournaments after /dt reload.
Removed
- CoreProtect soft-dependency. The old
integrations.core-protectand per-tournamentcore-protect.enabledsettings keep working, with a console warning, until you switch toanti-farm.
Upgrade note: older versions already saved tournament data, so a tournament that's running when you restart to install this update is resumed too. The same goes for a tournament cut short by an earlier restart, unless it has been started again since. If its end time already passed (within resume-grace-hours), it's finished and paid out instead.
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:uyp1kXM4:YA1a7y3X"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uyp1kXM4:YA1a7y3X"
}

