0.0.17
Compatibility
Changes
26.2 compatibility release — no code changes. This build marks Caravans verified on the released 26.2 line, on both supported servers:
- Full API-surface link-check against Paper 26.2 b62 — including its Adventure 5 bump, the one real plugin-breaker of the 26.2 cycle (Caravans calls none of the removed API).
- Clean live enable on Paper 26.2 b62 and Purpur 26.2 b2609 (Java 25).
api-version: '1.20'remains valid through 26.2. - Nothing in 26.2 touches the caravan surface: no llama/camel/donkey/mule/wolf/leash or horse-inventory changes. Piglins spawning on Peaceful just give guardians and wolf protectors valid Nether targets; sulfur-cave geysers shove a passing caravan no harder than any mob shove.
- Purpur: keep
mobs.llama.ridableat its defaultfalse— a WASD-ridable llama lets a rider steer against the caravan driver.
Identical code to 0.0.16 — already running that on 1.20–26.1? Nothing to rush.
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:Kg3BoahI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fA5OmaDl:Kg3BoahI"
}

