Links
Tags
Creators
Details
Licensed MPL-2.0
Published 3 months ago
Updated 4 days ago
All versions
0.5.1+26.3
Release
peterwolf's Splinecart 0.5.1+26.34 days ago 109
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client and server
Changes
0.5.1+26.3
- Port to Minecraft 26.3 (Wilderness Bound).
- Allowed minecarts on parallel tracks to pass each other smoothly without colliding or pushing each other apart (ignoring vehicle and passenger bounding box collisions between different track segments while preserving collisions between carts on the same segment).
- Fixed converging / merging track switches: joining ties now correctly register secondary incoming tracks (
prevAlt) and sync their switch blockstate. - Enabled bidirectional switch routing: when a minecart travels in reverse through a converging track tie (joining two tracks), redstone power now toggles which incoming branch (
prevvsprevAlt) the minecart takes. - Added the ability to toggle smoothing on track ties during building:
- Toggle default player smoothing preference via
/splinecart smoothing on|off|toggleor/splinecart smoothingto query. - Sneak + right-click in the air with Track Ties or Track item to quickly toggle default smoothing mode.
- Sneak + right-click directly on any track tie (with empty hand, Track item, or Track Ties item) to toggle smoothing on that specific tie.
- Right-clicking connected track ties with an empty hand now also toggles smoothing.
- HUD displays real-time track tie smoothing status (
Tie Smoothing: ON / OFF) and shortcut hints when aiming at a track tie during building. - Track building commands (
/splinecart build line,/splinecart build path,/splinecart connect) now respect player smoothing preferences.
- Toggle default player smoothing preference via
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:8k5WFoGm:ia09nnvo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8k5WFoGm:ia09nnvo"
}

