Tags
Creators
Details
0.9.1-1.21.1
Compatibility
Changes
As noted by kay-xr on github this update: Adds small, targeted bounds to path generation so road placement cannot run unbounded in a server tick.
PathStyles now have a maxFindYSteps value to prevent forever loops.
Failed path sections now have a maxSectionPlaceRetries value, after which the path will be marked as finished.
TravelersWatcher now has a maxSectionsPerTick value allowing the user to set how many path sections are attempted to be updated.
The same value have been added to the config for fine tuning.
maxFindYSteps (default: 96) maxSectionsPerTick (default: 2) maxSectionPlaceRetries (default: 12)
A big thank you to kay-xr for submitting these changes!
Happy Travels! ~Milamber
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:UuL8pBVf:aGw7SV2i"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UuL8pBVf:aGw7SV2i"
}

