2.1.5
Compatibility
Changes
SentientMobs 2.1.5
Config Migration System
Old configs are now handled automatically.
- Missing default values will be added automatically
- Outdated config versions now auto-update without resetting user settings
- Better compatibility with older plugin versions
Raid Defense Escalation
Villages are now far more reactive during raids.
During a raid:
- Villagers will immediately stop working
- Villagers will gather near the Supreme Leader
- One Iron Golem will protect the Supreme Leader
- Another Iron Golem will guard the Community Chest
New Raider Behavior
Raiders such as Pillagers can now steal items from the Community Chest.
Protect your village carefully
Village Improvements
Leadership Visuals
- Supreme Leader now glows red
- Council members now glow blue
Bug Fixes
- Fixed an issue where the Supreme Leader and Council members were not assigned correctly in newly created villages because all villagers started with the same level
Labor Villagers
Unemployed villagers can now trade as Labor villagers.
Features:
- Cheap trades
- Mostly basic/common resources
- Example items: seeds and starter materials
Leadership AI Changes
The Supreme Leader and Council members now:
- Work less frequently
- Spend more time patrolling and walking around the village
This makes village leadership feel more alive and dynamic.
Hostile Mob Fixes
- Fixed Zombies and Skeletons moving in a stuttering/jittery way under sunlight
- Hostile mob movement under sunlight should now feel smooth and vanilla-like again
Thanks for using SentientMobs More village simulation features are coming soon.
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:AMl59CQL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8no5Rtgr:AMl59CQL"
}

