1.0.0
Compatibility
Changes
Copper Boots
Inspired by AltarSMP.
Base item: Copper Boots
Command: /copperboots [player]
Permission: customweapons.copperboots (default: op)
Resource Pack: Install the AltarSMP Texture Pack - this plugin set is built around it and looks/sounds as intended with it installed.
Cross-Plugin Detection (/weapons)
Every AltarSMP weapon plugin registers /weapons [player], which hands you one weapon from every other AltarSMP plugin currently installed and enabled - a live check each run, nothing to configure.
Crafting Recipe
C C
C C
Where:
C= Copper Ingot
Drop the ingredients into a crafting table in that pattern (. = empty slot) to get the Copper Boots. Recipe can be turned off in config.
Enchantments
- Protection IV
- Feather Falling IV
- Depth Strider III
- Soul Speed III
- Unbreaking III
- Mending I
+3 Armor, +3 Armor Toughness, +0.1 Knockback Resistance on top of the piece's own base stats - matching a full Netherite armor piece regardless of the item's Copper material/look. The item is also unbreakable.
config.yml
weapon:
cooldown-ability-1: 15
cooldown-ability-2: 0
recipe:
enabled: true
shape:
- "CC"
- "CC"
ingredients:
C: COPPER_INGOT
Cooldowns are in seconds and reload from config on server start. Set recipe.enabled: false to disable crafting and hand the item out with /copperboots only.
Abilities & Triggers
| Trigger | Ability | What it does |
|---|---|---|
| Passive (while worn) | Copper Cushion | Cancels your fall damage automatically the moment you're actually wearing the boots on your feet. No button to press - right-clicking just tells you it's passive. |
Notes
- The weapon is bound to the player who receives it via a persistent NBT tag, so lore/name changes won't break ability detection.
- This is a passive item: its effect applies the instant it's worn in the boots slot and stops the instant it's removed, with no cooldown or trigger involved.
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:fv9uKKIi:eOSCKoY7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fv9uKKIi:eOSCKoY7"
}

