Tags
Creators
Details
All versions
2.0.0
Release
Create: Bits 'n' Tracks Community Edition 2.0.02 months ago 169
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
Added
- A settings screen, reachable from the Config button in the mod list, covering suspension, geometry, drive, friction, stress and sound values. Previously every one of them was fixed and could not be changed.
- Suspension can be switched on or off separately for loose cogwheels and for cogwheels that are part of a track.
Changed
- Renamed to Create: Bits 'n' Tracks Community Edition, shown in the creative menu as Bits 'n' Tracks CE. Existing worlds are unaffected, since block, item and recipe IDs are unchanged.
- A vehicle now travels at the speed its track links are moving, so its speed follows the size of its cogwheels and how fast they turn. Existing vehicles may run at a different speed than before.
Fixed
- Tracks slid across the ground instead of rolling along it, and mixing cogwheel sizes in one track made it worse.
- Every suspension cogwheel added to a track raised the vehicle's top speed.
- Heavier vehicles had a lower top speed.
- Cogwheels hovering just above the ground still pushed the vehicle along.
- A vehicle whose tracks were stopped slid downhill instead of holding its position.
- The game crashed when moving out of range of a vehicle running on tracks.
- Cogwheels added by other mods could crash the game once suspension physics reached them.
- Vehicles were flung into the air the moment their tracks touched the ground, and kept bouncing instead of settling after a drop.
- Physics stopped being applied to some cogwheels after another one was broken.
- Cogwheel chains did not follow a contraption when it was moved or rotated.
- Cogwheels sometimes rendered with the wrong chain texture.
- Blocks from other mods could be mistaken for cogwheels and given the wrong track collision size.
- Chain integrity warnings filled the log.
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:3db44CKX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:g9koB07q:3db44CKX"
}

