1.0.1
Compatibility
Changes
PotionSMP 1.0.1
This update focuses on bug fixes, ability improvements and balancing after the initial 1.0.0 release.
⚔️ Ability Changes
Sword
Fixed the Sword Auto-Crit passive not working correctly.
Axe
Improved compatibility with the current ultimate and critical-hit systems.
Bow
Improved arrow accuracy while using the Bow ability.
Improved arrow hit detection and general projectile behavior.
Homing arrows now behave more naturally without negatively affecting normal Bow shots.
Armor
Reworked the passive ability.
Landing 5 hits within 7 seconds grants Resistance I for 10 seconds.
Armor Ultimate now summons 8 Cave Spiders.
Improved summoned Cave Spider behavior.
Shield
Shield Ultimate now requires 25 successful blocks to charge.
During the ultimate, nearby enemies within 4 blocks receive Slowness I.
50% Damage Reflection remains active during the ultimate.
Defensive effects from the Shield ability have been improved.
✨ Ultimate System
Ultimate progress now resets when the player no longer meets the required potion conditions.
Ultimate progress resets after rerolling to another weapon ability.
A previously charged ultimate can no longer be saved by unequipping the required effects and equipping them again later.
Improved Ultimate Ready state handling.
🧪 Admin Commands
Added a new OP-only command:
/giveinfinitepotion <effect> [level]
This allows server operators to give themselves an Infinite Potion for testing or server administration.
🐛 Bug Fixes
Fixed multiple Bow projectile issues.
Fixed Sword Auto-Crit behavior.
Fixed ultimate progress being retained when it should reset.
Improved ability state handling after rerolls and potion changes.
Various balancing and reliability improvements.
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:ksvlohJU:LpCExtlA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ksvlohJU:LpCExtlA"
}

