Tags
Creators
Details
Licensed ARR
Published 11 months ago
Updated 7 months ago
All versions
1.0.8
Release
CobbleBetterNPC 1.0.88 months ago 114
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Dedicated servers only
Required content
Unavailable version
Unavailable version
Changes
Changelog — CobbleBetterNPC 1.0.8
Added
- Added an NPC reward system, allowing NPCs to give rewards both after being defeated in battle or without requiring combat, one of the most requested features.
- Full implementation and compatibility with behaviours, enabling much more advanced and modular NPC behavior control.
- Introduced new configuration subfolders, significantly improving file organization and overall scalability.
Behaviour Highlights
- player_textured Allows dynamically applying any player’s skin to an NPC, replacing legacy skin systems.
- npc_scale_configuration NPC visual size and hitbox can now be configured independently.
- battle_commands Allows executing different commands when the player wins or loses a battle against an NPC.
- wanders / wanders_water NPCs can freely move on land and in water.
- stationary Keeps the NPC within a defined radius and ensures it always returns to its configured coordinates.
- core / looks_at_players / panics / avoids_water / floats Enhance NPC realism with base behavior, player interaction, fleeing, floating, and water avoidance.
Changed
- When using behaviours, the
set skincommand has been removed, as a dedicated skin behaviour now exists. - Removed
maxDistanceFromSpawn. This is now fully handled by movement behaviours, allowing NPCs to walk freely while always returning to their configured position.
Fixed
- Fixed TPS drops when interacting with NPCs, significantly improving server performance.
- General optimization of interaction handling and behaviour execution.
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:aJnNiXsu:Xh8R2WTl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aJnNiXsu:Xh8R2WTl"
}

