Tags
Creators
Details
1.4.0
Compatibility
Changes
DonutShards 1.4.0 — Patch Notes
Release date: August 2026
Summary
DonutShards 1.4.0 merges missing YAML keys on upgrade, adds shop purchase confirmations and post-purchase commands, registers PlaceholderAPI placeholders, and ships bStats metrics plus a Modrinth update checker. The release jar targets Paper, Folia, Purpur, Spigot, and Bukkit on Minecraft 1.20.1 through 26.2.
Configuration merge
On enable and /shardmanager reload, the plugin deep-merges missing keys only from jar defaults into existing config.yml, messages.yml, shop.yml, gui.yml, and other managed files. Operator values are never overwritten. Upgraded servers automatically gain keys such as afk-joined without losing a custom prefix.
Shop
| Feature | Detail |
|---|---|
confirmation: per item |
Opens confirm/cancel GUI from gui.yml when enabled |
/shards confirmation on|off |
Player toggle stored in player-prefs.yml (default on) |
commands: per item |
Console commands after purchase with %player%, %uuid%, %item%, %price% |
PlaceholderAPI
Registered when PlaceholderAPI is present:
| Placeholder | Meaning |
|---|---|
%donutshard_balance% |
Viewer balance |
%donutshard_top_<1-10>% |
Player name at rank |
%donutshard_top_bal_<1-10>% |
Balance at rank |
Metrics and updates
- bStats plugin id 33616 — set
bstats: falseinconfig.ymlto opt out. - Modrinth update check — async check against project
4krPhA6H; ops are notified in-game when a newer release exists. Setupdate-check: falseto disable.
Commands
/shards top— shard balance leaderboard (top 10)./shardalias for/shards.
Build
- Artifact:
DonutShards-1.4.0-paper-folia-mc1.20.1-26.2.jar(shadow jar with relocated bStats). - Requires Java 21.
Compatibility
- Platforms: Paper, Folia, Purpur, Spigot, Bukkit
- Minecraft: 1.20.1 – 26.2 (see
release/supported-minecraft.json)
Upgrade notes
- Replace the jar and restart (or reload after swapping on a test server).
- Run
/shardmanager reloadif you only need message/shop merges without restart. - Existing
messages.ymlandshop.ymlkeep your values; new keys appear automatically.
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:4krPhA6H:NaSbotYr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4krPhA6H:NaSbotYr"
}

