Tags
Creators
Details
v2.2.0-beta.2+1.18.2
Compatibility
Required content
Changes
JCM v2.2.0-beta-2 for MTR 4.0.4 has been released!
This release brings back the MTR 3 lift arrival sound (The ding sound), enhance compatibility with NTE scripts and fix some issue.
Client & Server Update is required
Additions
-
- (Non-scripting) Revive the lift ding sound feature from MTR 3, now they should function mostly equivalently.
- Add
RawMeshBuilderandRawMesh, both are mostly API-compatible with NTE. - Add
generateNormal(),distinct()andtriangulate()toRawModel. - Add
customDestinationtoStop, which exposes the raw custom destination value. - Add
TickableSoundInstance, allowing sound parameters (e.g. volume/pitch) to be continuously adjusted throughout the playback, as well as the ability to stop the sound midway.MinecraftClient.stopSound()has been removed, you should use a TickableSoundInstance instead and stop withSoundManager.
- PIDS Scripting
- Add
PIDSBlockEntity.getTargetPlatformIds()to obtain the detected/selected platform id for ETA monitoring.
- Add
Changes
ModelDatahas been renamed toRawModel- DisplayHelper is now driven by
RawMeshBuilderinstead ofQuadDrawCall, this fixes an issue where the display may appear dimmer as intended. - Breaking: The
DisplayHelper.drawCall()method of drawing is removed, a DisplayHelper now contains a true 3D Model, you should use the drawModel/drawCarModel functions to render it out. - PIDS Projector is no longer culled, as it may result in large displays being cut-off.
Fixes
- Address a known issue in beta.1, where the stops data are incorrectly fetched across routes.
- Fix BackgroundWorker not getting interrupted on script reload, allowing submitted task to continue indefinitely.
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:nqHfqkgW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lQqKCDhg:nqHfqkgW"
}


