Tags
Creators
Details
1.2
Compatibility
Changes
What's Changed
Updated for Minecraft 26.3, plus a handful of fixes found while testing it there.
Added
- Tab completion for
/mcmmorewards, and a usage line when it's run without arguments. mmocore-xp.amountaccepts decimals.- The startup and reload messages say how many skills have rewards set up.
Changed
- Built against Paper 26.3 and mcMMO 2.3.001, and tested on Paper 26.3, 1.21.11 and 1.20.6. The jar is still Java 17 bytecode.
%skill%now readsMininginstead ofMINING.- Money rewards check that the economy actually accepted the deposit, and log it if it didn't.
- The project builds from a clean checkout: every dependency now comes from a public Maven repo
(it used to expect MMOCore and MythicLib jars in a
lib/folder that wasn't in the repo).
Fixed
- Rewards from the example config inside the jar no longer pay out on top of your own. Bukkit
fills gaps in
config.ymlfrom that built-in copy, so deleting an example reward (say the $500 at Mining 50) didn't remove it, and amoney-only reward still handed out the example's MMOCore XP. - Levels skipped over in a multi-level jump now pay out. mcMMO sends one event for a jump like
8 → 12, and only level 12 used to be checked, so an
every: 5reward at 10 was lost. - Level ups cancelled by another plugin no longer pay out (mcMMO takes those levels back).
- Skill sections written as
Mining:orMINING:are matched. Only exact or all-lowercase names worked before. - Money rewards work when the economy plugin enables after McMMORewards. Before, the economy was looked up once at startup, and money rewards stayed off for the whole session if it wasn't there yet.
- Reward commands written with a leading
/run instead of failing as an unknown command.
Upgrading
Drop in the new jar and restart. No config changes are needed, but read through your config.yml
once: anything you were getting from the built-in example config (see Fixed) stops paying out now.
Release Artifact
mcmmorewards-1.2.jar
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:PVKx14fa:VdSk0PfZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PVKx14fa:VdSk0PfZ"
}

