All versions
2.3.0
Release
Because broken behaviour simply won't do.4 months ago 8
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
SentientMobs Changelog v2.3.0
🐞 Bug Fixes
- Fixed an operator precedence issue affecting AI update throttling, ensuring entities are updated more evenly and consistently.
- Fixed villages being unable to spawn additional Iron Golems after the first one, allowing them to reach the configured maximum.
- Fixed Illagers occasionally pausing or appearing stuck between path recalculations when custom pathfinding is enabled.
- Fixed Community Chest deposits incorrectly reporting success when attempting to deposit invalid or empty items.
- Fixed loaded entity registration statistics occasionally counting ignored or unsupported entities.
- Fixed version comparison incorrectly handling non-standard version formats (e.g.
v2.3.0). - Fixed Village Politics takeover notifications persisting after a plugin reload.
Performance Improvements
- Significantly optimised Villager memory searches, reducing CPU usage on larger servers with many active entities.
- Reduced the overhead of Village Politics leadership visual updates.
- Improved squad management to prevent constant member reassignment and unstable leadership changes.
- Reduced unnecessary AI behaviour evaluations, lowering the performance impact of complex entity logic.
- Improved pathfinding responsiveness when following moving targets.
Improvements
- Improved Villager type detection for better compatibility and maintainability.
- Improved compatibility with non-Paper servers by refining fallback behaviour.
- Updated scoreboard colour handling to support newer Minecraft API versions.
- Improved Iron Golem behaviour selection, ensuring deterministic behaviour priorities.
- Removed several unused internal configuration options that had no functional effect.
- Performed general code clean-up, internal refactoring, and stability improvements throughout the plugin.
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:8no5Rtgr:T2VLuDnn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8no5Rtgr:T2VLuDnn"
}

