Links
Tags
Creators
Details
Licensed ARR
Published 8 months ago
Updated 8 months ago
All versions
1.0.0
Release
UnstablePotions 1.0.08 months ago 119
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
📋 Changelog
[1.0.0] — Initial Release
This is the first public release of UnstablePotions.
Added
- Core instability engine with five outcome types: Duration Shift, Amplifier Shift, Inversion, Side-Effect, and Jackpot
- Weighted random outcome selection with per-outcome enable toggles
- HMAC-signed potion tags for tamper detection and anti-duplication
- Per-potion rules: individual enable, inversion permission, and chance multiplier
- Potion list mode (NONE / WHITELIST / BLACKLIST)
- World gating with WHITELIST / BLACKLIST support
- Ingredient influence system (optional, off by default)
- Reroll-on-rebrew option (off by default)
- Full in-game Admin GUI with pages for: Brewing, Outcomes, Caps, Potion Rules, Visuals, World Rules, Performance, and Admin tools
- Save/Reload/Close controls inside the GUI
- Visual markers for unstable potions: name tag, lore lines, particle effects
- Particle rate limiting
- Amplifier and duration caps to prevent extreme outcomes
- Milk clears tracked side-effects (toggleable)
- Tipped arrow support (off by default)
- Lingering cloud special processing toggle
- Per-tick event budget for load management
- Suspicious-tag logging with cooldown and in-game notifications
- Internal metrics service tracking outcome type counters
- Audit service for tag correction events
- Commands:
admin,reload,debug - Permissions:
admin,reload,notify,bypass.unstable,bypass.negative,bypass.all - Auto-generated HMAC signature secret on first boot
- Config hot-reload via command and GUI
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:VWTxtA3x:LpdYdeFo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VWTxtA3x:LpdYdeFo"
}

