Tags
Creators
Details
1.4.0
Compatibility
Changes
V1.4.0 - 10/3/2026
- Mobs and items now have a new config option to include tracked stats as requirements! This means progression-based mobs and items are now possible. If any involved players meet the requirements, the mob or item will spawn.
- Added a few new default Power Mobs and a spawn key that involves this new progression potential. (Including a boss!)
- Added 6 new special items, a few of which were added to the loot of the new Power Mobs.
- Added 2 items to the loot pool of Random Power Mobs.
- Improved damage tracking to include special damage and potion effect damage.
- Changed player % damage requirement to count based on the collective % done by players vs. environment, not if one player reached that % of damage vs. other players %.
- Player-caused damage requirement is now needed to count as a tracked kill.
- Changed it so exp is spread between players relative to involvement in the fight instead of just the killer.
- Fixed a few cases to properly handle a player quitting mid-fight for tracking.
- Changed tracked max damage dealt to be the total damage done by a player to a Power Mob as a whole instead of just in one hit.
- Included max damage tracking to be integrated the same as the rest of the stats being tracked.
- Fixed custom items effect immunity to properly cause the apply_fail trigger instead of success when blocked.
- Added an update checker to notify plugin users if there is an update available.
- Fixed a bug in the UI that kept page numbers between different types of menu selections.
- Fixed a bug in the UI that was causing warnings of unsaved configurations when swapping pages mid-config deletion.
- Fixed an inaccurate statement found in the teleportation setting descriptions.
- Fixed it so summoned mobs from the summon ability can't pick up items.
- Changed the Summon ability to increase its chance to trigger based on the amount of health missing from the Power Mob.
- Fixes errors in the command description on how to use commands and added more suggestions for stat-based queries.
- Made the instructions atop config files update when the config is populated via command, so config files need to be regenerated less often on updates.
Recommended upon updating: Run "/powermob populate" for main, keys, items, and mobs to generate the missing configurations in config.yml or regenerate the files by deleting them.
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:LfYBH4eN:GxdMHuHs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LfYBH4eN:GxdMHuHs"
}

