Tags
Creators
Details
Licensed ARR
Published 3 months ago
Updated last week
All versions
1.0.6
Release
BetterPotionsExtended 1.0.63 months ago 125
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Spigot
Changes
π§ͺ Initial Release - BetterPotionsExtended v1.0.6
An advanced sandbox utility engine designed to seamlessly override, extend, and configure custom potion durations with fully interactive GUI controls!
π What's New
- Dynamic GUI Dashboard: Open an interactive interface with
/bpe potionsto configure durations live in-game. Bottles are custom-colored to match their actual in-game fluid visuals! - Easy +/- Time Adjustments: Left-click any configured potion to open the Modify Panel and adjust durations up or down in 30-second intervals using custom interface ingredients (Sugar, Redstone, Gunpowder, etc.).
- 1.21+ Trial Chamber Support: Built-in support for modern Trial Chamber status effects, including:
- Weaving πΈοΈ
- Wind Charged πͺοΈ
- Oozing π’
- Infested πͺ±
- Dynamic Tooltip Syncing: No more deceptive vanilla client tooltips! The plugin automatically hides vanilla durations and injects custom blue lore status lines (e.g.,
Speed (06:00)) matching your configurations. - Command Predictions: Full tab-completion engine added for
/bpe potions,/bpe reload, and/bpe give <player> <potion_type> [form]for fast and error-free admin workflows.
π§ Fixes & Optimizations
- Registry Translations: Resolved critical inconsistencies with internal Minecraft mappings (e.g., matching the
SWIFTNESSeffect backend smoothly to your custom config paths forSPEED). - Hot-Reload System: Instantly applies configurations to active items across all online players upon running
/bpe reload.
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:IWot8gez:ZB9PMJjM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IWot8gez:ZB9PMJjM"
}

