0.3.6
Compatibility
Changes
A. Added a vehicle radar showing scan effects, player direction and vehicle status. Radar targets can be clicked to inspect and manage vehicles
B. Improved query, preview and printing performance for large vehicles. Queries no longer scan continuously, reducing server load on large saves and reducing pauses during preview and printing. Dark vehicle previews have also been fixed.
C. Optimized vehicle teleportation. Teleporting a vehicle should no longer cause server stalls. Unloaded vehicles cannot be moved directly, but players can still teleport above them.
D. Improved compatibility for third-party Sable Blueprint welds and no-collision links, reducing abnormal pauses during restoration. Universal joints and giant hydraulic systems are also handled more reliably, and older blueprints remain supported.
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:5fUBLqeW:pcD0Yutw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5fUBLqeW:pcD0Yutw"
}

