All versions
2.0.0
Release
Crazymotives 2.0yesterday 19
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Visuals
- Restyled all Crazymotives blocks, entities and items to match vanilla Minecraft 26.3 pixel art, palettes and lighting (no sci-fi panels, no fullbright glow).
- Tiered minecarts (Wooden, Golden, Diamond, Netherite): new in-world textures and item icons.
- Wooden Rail and Copper Powered Rail (powered and unpowered): new textures and icons.
- 3-wide High-Speed Rail rebuilt as a timber, iron, gold tie-plate and redstone viaduct across flat, sloped and curved variants.
- Station block restyled in an observer / blast-furnace stone-and-iron design with a directional top arrow and redstone eye.
- Restyled Guide Book and Railway Map icons.
- Vanilla minecarts and vanilla rails stay completely untouched.
Gameplay & UI
- Stations now detect and dock minecarts already at rest on their rail (placed, pushed or stopped; any tier or vanilla) and emit comparator signal 15.
- 25-tick launch cooldown so launched carts do not immediately re-dock on brief redstone pulses.
- Launch route priority is now cart's own route, then rider's route, then station's route, so one player's station selection cannot override another player's route.
- Railway Map lets riders pick or clear their personal route anywhere. The Station screen supports typed renaming (1-36 characters, Enter to submit), line color cycling, launch facing rotation and launching a docked cart.
- Updated the Crazymotives Manual with crafting layouts for all 10 recipes and accurate speed numbers; all 10 recipes now unlock in the recipe book on join.
- Aligned the Golden Minecart (2-row pattern) and Guide Book (accepts any minecart or rail) recipes.
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:KkUjU56i:GyU9bfy0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KkUjU56i:GyU9bfy0"
}

