Tags
Creators
Details
Licensed GPL-3.0-only
Published 8 months ago
Updated 5 days ago
All versions
3.4.20+B-26.1.2
Beta
VO: Better Dogs 3.4.20+B-26.1.23 months ago 70
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client and server
Required content
Changes
[3.4.20+B-26.1.2]
Summary
The "Tamed Wolf Guard Mode" update. Adds guard mode behavior for tamed wolves.
- Guard Mode Activation: Right-clicking a tamed wolf with a bone toggles Guard Mode (consuming exactly 1 bone) and anchors the wolf to its current block.
- Mathematical Patrol Patterns:
- Aggressive: Paces in a circular/polygon shape along its outer perimeter sweep (80% range), pausing to scan outward for threats.
- Normal: Sit-sentry posture at the guard post (range = 0), or radial star patrols outward and back (range > 0).
- Pacifist: Close protective orbital circular pacing around the post.
- Auto-Targeting & Chase Caps: Normal and Aggressive guards automatically attack hostiles within their range (16/24 blocks) but are capped from chasing targets too far (20/32 blocks) to prevent them being lured away.
- Watchdog Alarms & Grace Buffs: Pacifist sentinels whine and emit warning note particles when hostiles approach, and optionally apply Regeneration and Resistance to owners/allies if
bd_pacifist_guard_buffsgamerule is enabled. - Subtle Foot Particles: Displays very subtle, non-distracting foot particles every 4 seconds (
ASHfor Aggressive,WHITE_ASHfor Normal,MYCELIUMfor Pacifist) to distinguish guard mode. - Manual Sitting Standby: Right-clicking with an empty hand sits the dog down manually, which temporarily pauses guard updates.
- Gamerule Customization: Added configurable patrol range rules (
bd_guard_patrol_range_aggressive,bd_guard_patrol_range_normal,bd_guard_patrol_range_pacifist).
Optional dependencies
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:e7H8SUmG:RwdJ1lbn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:e7H8SUmG:RwdJ1lbn"
}





