Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated 3 weeks ago
All versions
1.1.3
Release
Strength SMP 1.1.34 months ago 144
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
StrengthSMP v1.1.3 - Stability & Scaling Update
This update addresses mechanics with the Sword's Blink ability, fixes mathematical scaling issues for the expanded -10 to 10 strength limits, and prevents potential cooldown exploits.
๐ ๏ธ Bug Fixes
- Blink Ability Ground Clipping: Adjusted the raycast mechanics for the Sword's Blink ability to ignore minor downward looking angles. Players will no longer get blocked by flat ground when looking slightly down.
- Negative Strength Cooldown Exploit: Clamped the dynamic strength item cooldown calculation to a minimum of 3 seconds. This prevents players with negative strength (down to
-10) from bypassing the cooldown and spamming items. - Attacker Damage Multiplier Bug: Fixed a calculation error in the damage listener where negative strength attackers were having their damage reduced using the victim's defense reduction configuration instead of the attacker's per-strength damage config.
๐ Calculations & Scaling Improvements
- Standardized Multipliers: Simplified the damage and defense formulas to scale linearly across all strength limits (
-10to10):- Damage Multiplier:
1.0 + (strength * damage-per-strength) - Defense Multiplier:
1.0 - (strength * victim-reduction-per-strength)This aligns the gameplay math with the documentation inconfig.ymland eliminates division-by-zero or range boundary errors.
- Damage Multiplier:
๐ Configuration Changes
- Internal version bumped to
1.1.3.
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:ppfnRp2Y:UxxtEXlf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ppfnRp2Y:UxxtEXlf"
}

