Tags
Creators
Details
All versions
2.1.0
Release
2.1.02 months ago 3,738
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Unavailable version
Changes
Added
- A mod icon, shown in the mod list.
- Two settings. Suspension Speed Limit, under suspension, caps how hard a cogwheel can push off a surface, and Pivot Scrub, under friction, sets how freely the tracks let a vehicle turn.
Changed
- Tracked vehicles now turn at the rate their two track speeds call for, so running one track forward and the other back turns the vehicle on the spot. Existing vehicles will steer more sharply than before.
- Suspension is stronger by default and vehicles sit higher on it. Anyone who raised the suspension strength setting to compensate can lower it again.
Fixed
- Vehicles could not turn on the spot. The tracks slid sideways and the vehicle barely rotated.
- Breaking a vehicle into two parts could fling away the part that had a cogwheel on it.
- A cogwheel buried in terrain could launch the vehicle it was on.
- Enabling suspension on a cogwheel outside a vehicle dropped it by the full suspension travel.
- A suspension cogwheel's outline and hitbox stayed on the block grid while the cogwheel hung below it.
- Chain and belt selection, and the alignment lever's face selector, went by a cogwheel's grid position rather than where it was drawn.
- Tiny cogwheels used the small cogwheel's hitbox, and medium cogwheels used the large cogwheel's.
- Placing a vanilla chain or an industrial belt on a cogwheel that cannot take one showed a raw translation key instead of a message.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| bits_n_tracks-2.1.0-sources.jar | Sources jar | 272.15 KiB |
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:g9koB07q:duEsSo9r"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:g9koB07q:duEsSo9r"
}

