Links
Tags
Creators
Details
1.2.0
Compatibility
Changes
BetterMob v1.3.0 β Official Fabric Release (Minecraft 1.21.11)
BetterMob now officially supports Fabric! Bring advanced custom mobs, multi-phase boss fights, powerful skill mechanics, custom drops, and spawners to your Fabric servers and singleplayer worlds.
π Features on Fabric:
- Server & Singleplayer Ready:
- Dedicated Server: Runs on the server side. Vanilla clients (or clients with only BetterModel) can join without needing BetterMob installed!
- Singleplayer: Fully functional in local singleplayer worlds.
- BetterModel Integration: Native compatibility with
bettermodel-fabricfor custom Bedrock models and smooth animations. - YAML Mob Configurations: Define your mobs easily in
config/bettermob/mobs/*.yml(auto-generates example templates on first start). - Multi-Phase Boss Mobs: Set up health thresholds with dynamic display names, model swaps, equipment, and phase-transition skills.
- Skill Engine & Lifecycle Triggers:
- Triggers:
~onSpawn,~onDamaged,~onAttack,~onDeath,~onInteract, and periodic~onTimer. - Targeters:
@self,@target,@trigger,@entitiesinradius(@eir),@playersinradius(@pir),@nearestplayer(@p). - Mechanics:
damage,heal,message,actionbar,sound,velocity,potion,ignite,lightning.
- Triggers:
- Custom Drops: Drop tables with percentage chances, min/max item ranges, and custom experience drops.
- Mob Spawners: Player-range aware spawners respecting configurable mob limits.
- Commands:
/bettermob spawn <mob>and/bettermob reloadwith tab completion and permission checks.
π¦ Requirements:
- Minecraft:
1.21.11 - Fabric Loader:
>= 0.16.0 - Fabric API: Required
- Optional:
bettermodel-fabric(for custom models and animations)
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:Ub5HeGCV:qnKU2QGj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ub5HeGCV:qnKU2QGj"
}

