
Rainy 's Armor
This Mod adds Many more cool Armor such as TNT armor , frost armor and new swords and abilitys , a void sword and a frost spear and more , it also makes bedrock craftable and allows bedrock armor , basically a total of 6 new armor set and weopens
1.0.0
Compatibility
Changes
Rainy’s Armor
Rainy’s Armor is a progression-style Minecraft mod that adds 6 unique armor sets, powerful weapons, and special abilities that change how you play the game.
Each armor set introduces its own mechanics, effects, and playstyle, from mobility-based movement to high-damage combat abilities and utility tools.
Void Set

- The Void Armor is crafted using Ender Pearls
- Grants a custom Void effect when the full set is equipped
- Includes the Void Sword with its own abilities
- Part of the Abyss-themed progression system
Bedrock Set

- Bedrock is now craftable using a Bed + Cobblestone placed next to each other
- Unlocks the Bedrock Armor Set
- Includes the Bedrock Sword with a custom ability
- Comes with a unique Bedrock effect tied to the set
Slime Set
- Includes the Slime Armor Set
- Adds the Slime Sling
- The Slime Sling can launch the player into the air for mobility and combat
- One of the most fun and powerful utility items in the mod
Frost Spear

- Adds the Frost Spear weapon
- A powerful icy ranged/melee hybrid weapon designed for combat control
TNT Set

- Adds the TNT Sword
- Includes a custom TNT Sword ability
- Adds crafting recipes for the TNT Sword
- Focused on explosive combat playstyle
Summary
Rainy’s Armor focuses on 6 distinct armor sets with unique mechanics, including movement abilities, combat effects, and custom crafting systems, making progression feel rewarding and diverse.
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:lzUFY3jm:3Ml25as0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lzUFY3jm:3Ml25as0"
}
