
GodAmour
š”ļø God Armour Plugin ā Description God Armour is a powerful and highly customizable Minecraft plugin that introduces legendary, overpowered armor sets with special abilities, unique effects, and advanced protection. Designed for SMP, RPG, PvP, and custom
1.0.0
Compatibility
Changes
š”ļø God Armour Plugin ā Description
God Armour is a powerful and highly customizable Minecraft plugin that introduces legendary, overpowered armor sets with special abilities, unique effects, and advanced protection. Designed for SMP, RPG, PvP, and custom servers, this plugin allows server owners to create divine-level armor that feels rewarding, rare, and exciting.
Each God Armour set grants players enhanced stats, passive abilities, and special effects when worn, with optional full-set bonuses. Everything is fully configurable ā from stats and abilities to crafting recipes, permissions, and visuals ā allowing perfect balance for any server type.
⨠Key Features
Custom God Armour sets with unique names and lore
Powerful abilities like regeneration, fire immunity, speed, strength, and more
Full-set bonuses when all armor pieces are equipped
Custom crafting recipes or command-based rewards
Particle effects and visual auras
Permission-based access (LuckPerms supported)
Economy support via Vault
Lightweight, optimized, and lag-free
āļø Perfect For
Survival SMP servers
RPG & fantasy-based gameplay
PvP arenas and boss rewards
Donator kits and end-game items
š§ Fully Configurable
Server owners can customize:
Armor stats & toughness
Potion effects & abilities
Crafting recipes
Cooldowns & restrictions
Messages & permissions
š Why God Armour?
God Armour adds true end-game content to your server, giving players something legendary to grind for while keeping full control in the hands of administrators Made By SYLegendOP
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:tnff59xj:u7A3IqdH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tnff59xj:u7A3IqdH"
}
