Tags
Creators
Details
2.0
Compatibility
Changes
๐ Vitamin+ 2.0 โ Graphical Management & Enhanced Mechanics ๐
Vitamin+ 2.0 introduces intuitive graphical interfaces for module management and brings massive improvements to the Repair, Elevator, and Death Chest systems.
๐ฅ New Features
- Admin Module GUI (/vitamin module): Admins can now enable or disable modules globally through a new visual menu.
- Player Settings GUI (/vitamin pmodule): Players now have a personal menu to visually toggle their favorite features for their own gameplay.
โ๏ธ Module Updates
- Repair Tools Overhaul:
- Expanded Support: Now allows repairing Armor, Elytra, and Tridents.
- Intelligent Consumption: The system calculates and consumes only the materials needed for a 100% repair, automatically returning leftover materials to the crafting grid.
- Elevator Module Upgrades:
- Full Customization: Both the block material and the crafting recipe (shape and ingredients) are now fully configurable.
- Universal Use: Elevators are now public; any player with permissions can use any elevator on the map regardless of who placed it.
- Death Chest Enhancements:
- Explosion Proof: Chests are immune to TNT and Creeper explosions while they contain loot.
- Auto-Cleanup: The chest automatically vanishes with a smoke effect once the last item is removed.
- Weather Effects:
- Crop growth speed during rain is now configurable for better server balancing.
๐ฎ Removed Modules
- Carry On Module: This module has been removed from Vitamin+ as it has been moved to its own dedicated and improved plugin: Hold My Cow. Check it out for the best carrying experience!
๐ Bug Fixes
- Fire Aspect On Tools: Fixed a critical bug where the Fortune enchantment caused unintended block duplication (e.g., obtaining 4 Stones when mining 1 Cobblestone).
๐ Download now | Join our Discord for support!
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:wKw0THQX:YL9qgFJp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wKw0THQX:YL9qgFJp"
}

