All versions
1.1.0
Release
Advancement Rewards 1.1.04 months ago 388
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
A near-total rewrite — item rewards, a drag-and-drop web editor, in-game reward management, and a SQL data store.
Added
- Item rewards — grant items (with custom display name + lore via
&colour codes), money, or both for any advancement. New richconfig.ymlform alongside the simple money-only form. - Web editor (
/ar config) — a drag-and-drop browser UI to arrange rewards and push them to the live server. Per-player session links, server-side validation of every change, and an automaticconfig.yml.bakbackup before each apply. - In-game reward management —
/ar list,/ar advancements(browse every advancement on the server — vanilla, datapack, or mod),/ar add, and/ar remove, so rewards can be managed without editing files. - Any advancement — vanilla, datapack, and mod/plugin-added advancements are all supported.
- Economy provider selection — choose the Vault provider (
auto/Essentials/CMI/ custom) inconfig.yml. Works without Vault for item-only setups. - SQL player data — claim tracking moved to SQLite (default) with optional MariaDB, configured in
config.yml. Asynchronous and cached so the main thread never blocks; legacyplayerdata/*.ymlfiles are imported automatically on first start. - Multi-platform support — one jar runs on Paper, Purpur, Spigot, Bukkit, and Folia, with no extra setup on any of them.
Changed
- Supports a wide version range: Minecraft 1.18 – 26.1.2.
- Permissions reworked to
ar.reload,ar.edit, andar.admin(replacingadvancementrewards.reload). - Cleaner, paginated chat output with clickable controls for
/ar listand/ar advancements. - Improved update notifications and metrics.
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:k2bHm5jx:bjMiwF89"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k2bHm5jx:bjMiwF89"
}

