Links
Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated last week
All versions
1.19.2-3.6.2
Beta
YMTR Fabric 1.19.2 3.6.2last week 47
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Fabric
Supported environments
Client and server
Changes
1.19.2 3.6.2:
Please note that the version number is not aligned with 1.20.1! It does not include all update contents of 1.20.1 3.6.3.
- Fixed known issues, improved stability, and optimized the experience.
- Synced the following updates from 1.20.1 YMTR 3.6.2:
- *Temporarily unavailable. [Beta] Added the "Track Data Editor", allowing arbitrary data to be written to tracks.
- Fixed the issue where track distance adjustments were ineffective; tracks that exceed the original mod's render distance can now be displayed.
- Added a new rendering mode for platform screen doors: "Current Station + Line Map".
- Fixed an issue where station stop times would become disordered when multiple routes with independent dwell times were assigned to the same depot.
- Synced the following updates from 1.20.1 YMTR 3.6.3:
- Full-height platform screen door panels now correctly display formats in the semi-transparent state after being cut with shears.
- Line map signboards can now correctly display loop lines.
- Fixed the issue where loop lines displayed the same station twice.
- Loop lines can now display counter-clockwise looping lines in a counter-clockwise direction.
1.19.2 3.6.2:
请注意版本号与1.20.1不对齐!未包含1.20.1 3.6.3所有更新内容
- 修复已知问题 改善稳定性 优化体验
- 同步以下1.20.1 YMTR 3.6.2更新的内容:
- *暂不可用 [Beta]新增“轨道数据编辑器”,可以向轨道写入任意数据
- 修复轨道距离调整失效的问题,现在可以显示超出原版渲染距离的轨道
- 屏蔽门新增“当前站+线路图”渲染模式
- 修复同一车厂设置多个包含独立停站时间路线时,停站时间错乱的问题
- 同步以下1.20.1 YMTR 3.6.3更新的内容:
- 全高屏蔽门吊板在剪刀剪后的半显状态下能正常显示格式
- 线路图立牌可以正常显示环线
- 修复环线显示两次同一车站的问题
- 环线能够逆时针显示逆时针循环线
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:U75MCH6y:kQm0q7X7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:U75MCH6y:kQm0q7X7"
}

