All versions
18.0.mod
Release
Vanilla+ | Version 18.0 (Mod)last year 2,434
Compatibility
Minecraft: Java Edition
1.21.7–1.21.8
Platforms
Fabric
Forge
NeoForge
Quilt
Supported environments
Server-side
Singleplayer
Changes
Iron Hammer, Tweaked textures, 3D Food, and Mexican Spanish support!
This update is small in terms of new features, but I've also manually translated every item in the data pack into Mexican Spanish! Read more below.
- Iron Hammer: this is crafted with 5 iron blocks and 2 sticks. It's meant to be reminiscent of an early game Mace, but its real advantage is that it can be used as both a tool and a weapon. It has the capabilities of an Iron Pickaxe with double the durability, but its only supported enchantments are for the Pickaxe aspect of it. However, it has an attack speed between Swords and Axes, and deals some base knockback!
- 3D Food: I'm in the process of making 3D models for every food item in the game! These are accessed by renaming the food in an anvil and adding "Dish" (or in Spanish, "Plato") after the name! You can place them in item frames so that the frame is completely covered. This is inspired by resource packs that feature 3D food! See the image below on how to do it.

- Texture Changes: With the announcement of Copper Armor and Tools coming to the base game, I've changed the item textures to match the Vanilla textures. I've also changed the model textures for Copper and Emerald Armor. Side note, the Copper Gear in this pack WILL BE REMOVED once it is added to the Vanilla game.
- Spanish Translations: In real life, I'm studying Spanish, so I decided to manually translate every item and advancement in my data pack to Mexican Spanish! Now, when you turn on "Español (MS)" in Minecraft, any item crafted after this update will now be translated into Spanish!
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:9eokjKUM:Civh11wH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9eokjKUM:Civh11wH"
}

