Links
Tags
Creators
Details
All versions
0.1.0-unofficial.6+26.2
Beta
Datapack components for Minecraft 26.22 months ago 435
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Datapack component update for Minecraft Java 26.2.
Added
- Added a synced
riautomobility:frame_behaviordynamic registry for optional seat switching, integrated-engine rendering, and attachment rules. - Added conservative defaults so unrelated third-party frames are unchanged unless their datapack explicitly opts into RIA behavior.
- Rebuilt ExamplePack around the current Automobility frame, wheel, recipe, and resource-model formats for Minecraft 26.x.
Changed
- RIA frame behavior is now resolved by component registry id instead of relying on model namespaces, allowing custom packs to use their own namespace safely.
- Updated project and Modrinth copy from Alpha to Beta and removed obsolete claims that lorry cargo and mounted seat switching were unavailable.
Fixed
- Corrected the ExamplePack buggy's frame orientation, wheel origin, wheelbase, seat placement, and integrated-engine presentation so its custom model renders as one coherent two-seat off-road vehicle.
Validation
- Added codec and resource-contract tests for the example frame, wheel, model, and synchronized RIA behavior definitions.
- Passed the complete automated test suite and a clean release build on both supported Minecraft branches.
- Loaded the ExamplePack on a dedicated 26.2 server and verified the custom buggy's model, wheel placement, resource reload, and integrated-engine rendering in a real connected client.
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:OZ1lM8wy:baq2kYJI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OZ1lM8wy:baq2kYJI"
}

