4.0.8
Compatibility
Changes
SkyTrainFolia 4.0.8
中文
这是自 Modrinth 2.1.4 以来的一次较大更新:
- 新增手动列车的实验性 MA/ATP 保护、速度与授权终点监督,以及司机提示;内置伪 ATO 仍使用独立的驾驶逻辑。
- 改进双端驾驶席、换向器和 Hotbar 操作;单个 JAR 支持 Shiroha 26.2 与 26.3。
- 新增列车完整性监测(TIMS)。完整性异常时保持制动,并提供停稳后的确认恢复流程。
- 改进伪 ATO 的站前减速与
V_target保速:更新目标速度时显示聊天提示,修复达到目标速度后再次拉到 P4 的问题。 - 修复进站提示重复的
[SkyTrain]前缀,并改进 TIMS 停车原因及/st start的反馈。
升级提示: 使用完整 SkyRail Suite 功能时,请配套更新GitHub仓库内的 STCS 4.0.6、SkyworldTrainAPI 2.1.4 和 SkyPCC 2.0.3。升级前备份列车及线路数据;旧存档中的列车首次启用 TIMS 后可能需要停稳执行 /st tims ack。本版已通过 26.2/26.3 构建与自动测试,实际线路验收仍在进行。
English
A major update since the 2.1.4 release on Modrinth:
- Added experimental MA/ATP protection for manually driven trains, including speed and authority-end supervision and driver guidance. Built-in pseudo-ATO remains a separate driving mode.
- Improved cabs at both ends, reverser and hotbar controls. One JAR supports Shiroha 26.2 and 26.3.
- Added train integrity monitoring (TIMS), with a brake hold on integrity faults and an acknowledgement procedure after the train has stopped.
- Improved pseudo-ATO station approach and
V_targetspeed holding. Target changes now appear in chat, and reaching the target no longer causes an unexpected return to P4. - Fixed the duplicated
[SkyTrain]station-message prefix and clarified TIMS stop reasons and/st startfeedback.
Upgrade note: For full SkyRail Suite functionality, download STCS 4.0.6, SkyworldTrainAPI 2.1.4 and SkyPCC 2.0.3 from GitHub page and use them together. Back up train and railway data before upgrading. Existing saved trains may require /st tims ack while stopped after their first TIMS check. Builds and automated tests passed on 26.2 and 26.3; live railway validation is still pending.
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:O3Hawscb:aAB87e37"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O3Hawscb:aAB87e37"
}

