
Hostile Captains
Hostile Captains enhances Minecraft’s hostile mobs by giving them a chance to naturally spawn as powerful Captains or Apocalypse Super Captains. Four Captain variants and one Super Captain variant are available for zombies, skeletons, guardians, creepers,
0.2.0
Compatibility
Changes
Hostile Captains 0.2.0: Nether
The Nether has gained five new hostile captain families, each with four Captain variants and one powerful Super Captain.
Added Captain Families
- Piglin: Gilded Raider, Crossbow Commander, Firebrand, Bastion Guard, and the Golden Warlord Super Captain.
- Piglin Brute: Axe Enforcer, Berserker, Shieldbreaker, Bastion Executioner, and the Blackgold Tyrant Super Captain.
- Zombified Piglin: Rotblade, Soulbound Legionnaire, Wrath Caller, Hellfire Revenant, and the Undying Legionnaire Super Captain.
- Hoglin: Tusk Guard, Stampeder, Warpscarred Hoglin, Ravager Hoglin, and the Infernal Colossus Super Captain.
- Zoglin: Plague Tusks, Bonecrusher, Feral Howler, Rotten Stampeder, and the Famine Incarnate Super Captain.
New Abilities
- Enchanted gold, diamond, and netherite weapons and armor.
- Crossbows with Piercing and Quick Charge.
- Fire Aspect weapons and fire resistance.
- Berserker phases when Piglin Brutes reach low health.
- Captain auras that strengthen nearby Piglins and Zombified Piglins.
- Poison, Hunger, Weakness, Slowness, Nausea, Regeneration, fire, and powerful combat buffs.
- Unique health, damage, movement speed, armor, and knockback profiles for every new Captain family.
- Nether Captain and Super Captain particles, with no visible name tags.
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:FXRtZung:X7ZkNTIC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FXRtZung:X7ZkNTIC"
}
