Links
Tags
Creators
Details
0.9.6
Compatibility
Changes

Without Honor: NPCs, Update 0.9.6
In 0.9.4-0.9.5 a bug crept into the provocation system that made combat NPCs noticeably dumber - found it, took it apart down to the last screw, and fixed it. No new features, fixes only.
Combat AI back in shape
The root was a single bug: provocation "forgiveness" wrongly dropped any player target once a second - even one assigned via "Who to attack".
Forgiveness itself isn't gone - it works as intended: the NPC only lets go of someone who hit it themselves and hasn't touched it in a while. Assigned enemies don't get "forgiven".
Also fixed
- An NPC with an active schedule could teleport to its schedule spot mid-fight. The schedule now politely waits for the fight to end.
- "Flee when hurt" on combat styles: the panicking NPC first aggroed from the very first hit and only then ran. It now honestly runs, and provocation stays intact.
- Natural hostility: a combat villager-NPC fled from undead instead of fighting, and feared a predator even with its hostility turned off. Prey now fears only real predators - and only while not in a fight itself. How's that for a line, huh?
- After a chunk reload the mage could assemble its spells without the book ones - the spellbook in the accessory slot is now always counted.
- Invulnerable decorative NPCs no longer gather a crowd of mobs endlessly punching thin air around them.
- A defender golem no longer gets a permanent target over an accidental poke at an NPC - it steps in only for a real offense.
- The preview on the Pose tab now shows the per-part pose and the idle emote if they're set. Rotation and position of the transform no longer push the model out of the frame - it stays centered.
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:z3LQpsHg:4Y8H2BIA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:z3LQpsHg:4Y8H2BIA"
}

