Links
Tags
Creators
Details
1.0.7-1.20.1
Compatibility
Required content
Changes
π¦ Railway Evolution v1.0.7 BETA β The Dispatcher Update! ποΈπ°οΈ v1.0.7 elevates traffic management to modern metro standards! Your trains are no longer just moving; they are coordinated by the "Eye of God." We've implemented a global dispatching system to eliminate collisions once and for all.
β¨ What's NEW in v1.0.7: ποΈ Global Dispatcher ("Eye of God"): Centralized monitoring system. Every train now reserves its path in advance. If a segment is occupied, the AI automatically triggers smooth deceleration, preventing accidents without the need for manual signaling!
π¦ Smart Siding (Conflict Resolution): Head-on collisions on single-track lines are a thing of the past! The Dispatcher analyzes oncoming traffic and automatically routes lower-priority trains to the nearest siding to let oncoming traffic pass.
π°οΈ Smart Path Reservation: New route planning logic. Trains "negotiate" right-of-way using the 1xCodeteam global registry.
βοΈ Under the Hood (Optimization): π Extreme Performance Boost: Weβve refactored AI logic ticks. Calculations for secondary systems (Highbeams, Greetings, Sensors) now run every 5 ticks. This saves up to 60% CPU resources!
π’ Smooth Braking Physics: Updated deceleration algorithm. Upon detecting an obstacle or path reservation, the train sheds 15% speed per tick, ensuring a soft and realistic stop.
π Network Sync 2.0: Improved Server-to-Client data transfer. The Dispatcher broadcasts the network state every 20 ticks for perfect synchronization.
β Why Update? v1.0.7 makes your railway truly autonomous and safe. This is our most massive technical update yet, maintaining high FPS (only ~5 FPS impact with 10 active trains!).
Special thanks to our 268+ pioneers! We are building the future of autonomous logistics together. ππ¦Ύπ₯
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:VcPwJKGX:Xp9u1ZEU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VcPwJKGX:Xp9u1ZEU"
}

