All versions
1.3.0
Release
KurumaExampleCarPack 1.3.03 weeks ago 44
Compatibility
Minecraft: Java Edition
1.21.1
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Kuruma Example Car Pack 1.3.0
English
- NeoForge 1.21.1 support. The same jar now works on both Forge 1.20.1 and NeoForge 1.21.1.
- New "Sample Wheels" part. An example wheel part with its own mesh and texture. Copy it when you make a wheel.
- The Deep Dish Wheels part's default offset is now 0 (it used to sit 7 cm outward).
- The part definitions now include a comment showing how to use
carsto limit which cars a part fits.
Included for creators
- The README and MODELING.html are merged into
PACK_CREATE_GUIDE.html. It has separate Car, Wheel and Parts pages, a chapter on replacing sounds, and appendices listing every spec and part key. tools/is renamed tomodeling_tools/(the Blender gauges).- New
sound_tools/make_octave_up.py. It builds the high-rpm exhaust loop (exhaust_high) one octave up without adding a seam.
Requirements
- Kuruma 1.6.0 or later (on both Forge 1.20.1 and NeoForge 1.21.1)
日本語
- NeoForge 1.21.1 に対応しました。 Forge 1.20.1 と NeoForge 1.21.1 のどちらでも、同じ jar をそのまま使えます
- 「サンプルホイール」を追加しました。 自前のメッシュとテクスチャを持つホイール部品の見本です。ホイールを作るときはこれをコピーしてください
- 「深皿ホイール」の既定のオフセットを 0 にしました(以前は 7cm 外へ出ていました)
- 部品の定義に、付けられる車種を絞る
carsの書き方をコメントで添えました
作る人向けの同梱物
- README と MODELING.html を
PACK_CREATE_GUIDE.htmlに統合しました。車・ホイール・パーツのページに分かれ、音の差し替えの章と、諸元・部品の全項目の付録があります tools/をmodeling_tools/に改名しました(Blender のゲージ)sound_tools/make_octave_up.pyを追加しました。高回転用の排気音(exhaust_high)を、継ぎ目を増やさずに 1 オクターブ上へ作れます
必要なもの
- Kuruma 1.6.0 以降(Forge 1.20.1・NeoForge 1.21.1 とも)
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:wvJeLHUc:Q5tVTVEF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wvJeLHUc:Q5tVTVEF"
}

