Tags
Creators
Details
Licensed MIT
Created 4 years ago
All versions
v2.2.0-beta.3+1.19.4
Beta
[Fabric 1.19.4] v2.2.0-beta.32 months ago 36
Compatibility
Minecraft: Java Edition
1.19.4
Platform
Fabric
Supported environments
Client and server
Required content
Changes
JCM v2.2.0-beta.3 for MTR 4.0.4 has been released!
Additions
- (Non-scripting, MC 1.19.4 or above) Add mouse hover tooltips in the MTR Dashboard, showing more details about a platform/siding.
- Add
RenderManager.drawModel(model: Model | DynamicModelHolder, matrices: Matrices?)as an easy way to draw a model.- This ought to replace
ModelDrawCalland all variants ofdrawModel/drawXXXModelin favor of a unified RenderManager. - Of course compatibility is still retained, no code has been removed.
- This ought to replace
- Allow passing in a
DynamicModelHolderfor all places where aModelis accepted as a parameter for rendering.- The need to use this over
getUploadedModelis explained in the documentation. (Avoid using getUploadedModel() for rendering)
- The need to use this over
- Add
VehicleScriptContext.getCarBogieRenderManager()for rendering with transformation of the bogie. - Add
RawMeshBuilder.asRawModel(): RawModelas a quick way to obtain an instance ofRawModel.- Equivalent to
new RawModel()andRawModel.append(rawMesh: RawMesh).
- Equivalent to
- Add more overload for
GraphicsTexture.upload(), allowing for uploading selected portion of image to conserve performance.
Changes
Resources.getNTEVersion()now returns the current Minecraft version in use, instead of hard-coded to "1.19.2".- Scripted PIDS now also shows an in-game error in the chat, with script debug mode enabled.
Fixes
- Fix Forge version crashing with some mods sharing the same config library as JCM.
- (Non-scripting) Fix JCM PIDS auto platform detection range, now the platform detected should behave the same as MTR PIDS.
Download:
You can download this release on Modrinth, CurseForge or GitHub
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:lQqKCDhg:xT4b6ehH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lQqKCDhg:xT4b6ehH"
}


