0.0.16
Compatibility
Changes
Performance pass. No new features, no behavior changes you can feel — the hot paths just got leaner. Re-verified against current servers: one jar spans 1.20 → 26.x (API surface checked against Paper 26.1.2 stable with 26.2 tracked; 26.x servers run Java 25, and the plugin's Java 21 build runs there unchanged).
- Walkability probes fetch each block once — the movement core's innermost loop re-fetched the same blocks up to 3×.
- Straight-line cruise stopped re-validating its heading twice a tick (the "never smooth into a wall" guard still runs on every turning tick).
- Parked animals go network-silent — one zeroing send, then nothing until something actually shifts them. No more per-tick velocity packet per idle animal while you sort chests.
- Guardians scan smarter — Paper's filtered entity query, and after ~2s with nothing in range they relax to a staggered 1-second cadence, snapping back on first contact. Targeting and the water-float valve are untouched.
- The auto-store fullness poll stopped cloning cargo and no longer decodes the saddlebag stash — counts live beside the data now (old stashes migrate on first read).
- The storage-run boss bar only sends what changed — it was renaming itself every tick.
- Fixed:
/caravandrive(op-only) called a 1.21-only look API directly and broke on 1.20.x servers; it now degrades gracefully like the rest of the movement core.
26.2 verification (2026-07-17): this exact jar re-verified against the released 26.2 — full API-surface link-check against Paper 26.2 b62 (including its Adventure 5 bump) and a clean live enable on both Paper 26.2 b62 and Purpur 26.2 b2609 on Java 25. No changes needed. On Purpur, keep mobs.llama.ridable at its default false so a rider can't steer against the caravan driver.
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:fA5OmaDl:47JPnIxn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fA5OmaDl:47JPnIxn"
}

