Tags
Creators
Details
1.0.0
Compatibility
Changes
I am excited to announce the first public release of VitalVials, a unique Minecraft plugin for Spigot/Paper servers (1.21.x).
VitalVials introduces a new gameplay mechanic where players can trade their health for powerful effects, creating a balanced risk–reward system. With full customization options, server owners can fine-tune costs, mechanics, and player experiences to fit their server’s style.
✨ Features
- Health-Based Economy: Players exchange their max health or health points for powerful effects.
- Fully Configurable: Customize every aspect of effects, costs, cooldowns, and mechanics via
config.yml,effects.yml, andactivation.yml. - Dynamic Scoreboard: Real-time tracking of active effects and durations, customizable per player.
- Player-Specific Settings: Players can toggle and personalize their scoreboard.
- Cooldown System: Prevents effect spamming with per-effect cooldowns.
- Refund System: Refund effects with configurable percentages for added balance.
🛠 Installation
- Download the
VitalVials.jarfrom this release. - Place it into your server’s
plugins/folder. - Restart the server to generate configuration files.
- Adjust settings in
config.yml,effects.yml, andactivation.yml. - Use
/vv reloadto apply changes without restarting.
📜 Commands
/vv→ Main command./vv reload→ Reloads configurations./vv shop→ Opens the effect shop./vv buyEffect <effect>→ Buy an effect directly./vv viewStatus→ Shows active effects./vv scoreboard <on/off/editShort>→ Toggle or customize the scoreboard./vv refundEffect <effect>→ Refund an effect./vv removeData <player/allPlayer>→ Clear player data.
🔑 Permissions
vv.admin→ Full access.vv.reload,vv.shop,vv.buyEffect,vv.viewstatus,vv.scoreboard,vv.refundEffect,vv.removedata.
📌 Notes
- Tested with Minecraft 1.21.x on Bukkit/Spigot/Paper.
- Highly configurable — see README and configs for details.
- Licensed under the MIT License.
This is the first official release of VitalVials — feedback, issues, and contributions are welcome! 🚀
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:TYvJp17D:iJLcpABr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TYvJp17D:iJLcpABr"
}

