Tags
Creators
Details
v2.3.0-prerelease.2+1.20.1
Compatibility
Required content
Changes
JCM v2.3.0-prerelease.2 for MTR 4.0.5 has been released!
This is a prerelease, focused on bug-fixes and preparation before the official release.
General
MTR Patch
- Attempt to fix the "infamous" BVE Motor Sound bug in MTR 4, where an unrendered vehicle would result in the sound getting stuck.
Technical
Scripting
- PIDS Scripting - The newly added "Rectangle" has been renamed to "Rect"
- This is to avoid name conflict of existing scripts using AWT's Rectangle.
- Add
Resources.ANTE_FLAGso scripts do not error out, though it is set to false. - Add basic compat for
SoundHelper/TickableSoundin ANTE. - Added the dummy
Resources.mgr()alias that previously existed in NTE. - Add
Resources.id(id: Identifier, suffix: String)to obtain a new identifier withsuffixbeing appended to the path.- Can be used with a "base path" via
idr(), then resolving it in runtime with this function.
- Can be used with a "base path" via
- If you invoke a Java method with an "undefined" as one of its parameter, it will show a very long
Can't find method...error, since it cannot match the method signature.- The Rhino Undefined class will now be replaced with
UNDEFINEDin the error message, instead of the full class name. - An extra warning will be shown in console, notifying that you have passed an undefined object as one of its param.
- The Rhino Undefined class will now be replaced with
- Fix
ConcurrentModificationExceptionwhen reading resources during Runtime Stage in previous beta release.
Translations
Thanks to the following people who have contributed translations for this release! (No particular order):
- Paaaaddy (ga_ie)
Translations for JCM is now hosted on ZiYue's Weblate
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:6NhEcal4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lQqKCDhg:6NhEcal4"
}

