All versions
1.1.0
Release
Fighter Mod 1.1.0last month 51
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
Forge
Supported environments
Client and server
Changes
Changelog
[1.1.0] — 2026-09-18
✨ Added
- Gluttony Amulet
- Right-click in off-hand: -4 HP, +6 hunger, +4 saturation, Regeneration for 3 seconds.
- 3-second cooldown, 1 durability per use.
- No health/durability cost in creative mode.
- Iron Vampiric Blade
- On hit: restores 2 HP (1❤), consumes 2 hunger.
- 250 durability, RARE rarity, repairable with gold ingots.
- Netherite Vampiric Blade
- On hit: restores 3 HP (1.5❤), consumes 2 hunger.
- 500 durability, EPIC rarity, fire resistant, repairable with netherite ingots.
- New synergies
- Critical Amulet + Critical Sword → ×3 damage, consumes 2 hunger.
- Critical Amulet + Vampiric Blade → ×1.5 damage, no hunger cost.
- Speed Amulet + Vampiric Blade → speed activation is free.
🔧 Changed
- Critical Amulet now accounts for new weapon types and synergies.
- Speed Amulet correctly removes its effect when the player stops moving or loses the amulet.
- Updated crafting recipes and item tooltips.
🎮 Recipes
- Gluttony Amulet
BIB
IRI
BIB
B = Bone I - Iron Ingot R = Rotten Flesh -**Iron Vampiric Blade
B
I
S
B = Bone I = Iron Ingot S = Stick
- Netherite Vampiric Blade Smithing upgrade:
- Template: Netherite Upgrade Smithing Template
- Base: Iron Vampiric Blade
- Addition: Netherite Ingot
🐛 Fixed
- Fixed amulet effect removal on item loss.
- Minor stability and performance improvements.
[1.0.0] — Initial Release
✨ Added
- Critical Amulet — ×2 damage, consumes 2 hunger per hit, 100 durability, 0.5s cooldown.
- Speed Amulet — Speed II while moving, consumes 1 hunger, 10s cooldown.
- Critical Sword — works with Critical Amulet, no hunger cost when amulet is active.
- Crafting recipes for all items.
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:W56ohKac:YVGSfLvl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:W56ohKac:YVGSfLvl"
}

