Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated last month
All versions
1.2.0
Beta
Warband 1.2.05 months ago 33
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
1.2.0
- Added Illager War advancements, including mansion entry, faction milestones, bounty, crusade, and Warmarshal kill progress.
- Added modded stronghold support: Illager Invasion forts/labyrinths are faction camps, and The Lost Castle is a faction seat.
- Added new hostile tactics: spider ceiling crawl, elevated-target hops, ranged repositioning, stealth/status-aware detection, bogged poison back-dash, stray jump shots, and more reliable Enderman disrupt/provoke behavior.
- Added optional Overworld depth difficulty for harder deepslate caves, with
/warband difficultyshowing raw/applied depth bonus. - Added the bounty hunter overhaul: diamond gear, melee/ranged weapon swapping, parkour pursuit, taunts, glowing mark, stalk teleport, one revive, ominous summon cue, and
/warband debug bounty. - Added faction-war escalation and feedback: heat states, war/crusade patrols, in-world event cues, better witness rules, and clearer
/warband intel. - Changed config presets to
CUSTOM,VANILLA_PLUS(vanilla+accepted), andFANTASY; Vanilla+ disables the more RPG-facing systems by default. - Changed REGIONAL spawn protection:
safeRadiusnow applies in REGIONAL mode, with a separateregionalSpawnRampBlocksramp and tighter defaults. - Fixed Warmarshal Illusioner conversion reliability in worlds without Illager Invasion.
- Fixed revenge and bounty patrols not immediately pathing toward the target player.
- Fixed revenge and bounty leader nametags rendering through walls.
- Fixed rare false-death states where normal Warband-stamped mobs could play death animation/audio but keep fighting.
- Fixed faction heat not tracking when bounty hunters were disabled.
- Fixed revenge grudges expiring from missed random spawn rolls instead of real failed spawn attempts.
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:d0onuC0a:3W8RiMWH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:d0onuC0a:3W8RiMWH"
}

