Links
Tags
Creators
Details
1.0.8-1.20.1
Compatibility
Required content
Changes
π Railway Evolution v1.0.8 β The Vanilla Edition Railway Evolution 1.0.8 is the definitive optimization update. Weβve stripped away the complexity to achieve peak performance. This is the final stable build for Forge 1.20.1, as development will now shift towards newer versions of Minecraft in the coming weeks.
π Whatβs NEW in v1.0.8 (Vanilla Refactor): π Extreme Optimization: Weβve removed over 28 redundant files and 300+ lines of bloated code (Dispatcher, Heatmaps, Network Packets). The mod is now lighter, faster, and more stable. Experience 120+ FPS with 10+ active trains on 32-chunk render distance!
π§ Refined AI Controller: The train intelligence has been completely overhauled. Weβve eliminated the heavy v1.0.7 dependencies, leaving only the essentials: Graduated Braking and a highly optimized pathfinding logic.
π¦ Lightweight Performance: By removing the global registry and complex network syncing, weβve reduced server-side impact to near zero. No more lag spikes on high-speed rail lines.
π‘οΈ Core Safety System: Player detection, whistle alerts, and emergency braking are now hardcoded into the base AI, ensuring reliability without the need for external managers.
β οΈ IMPORTANT NOTICE: Final 1.20.1 Release: This is the last planned update for Forge 1.20.1. No new features will be added to this version.
The Future: Development is moving forward! Expect updates for newer Minecraft versions starting in the following weeks.
Clean Slate: Due to the removal of the v1.0.7 Dispatcher system, old config files may be incompatible. A fresh install is recommended.
Special thanks to our 361+ pioneers! Weβve made this mod as fast and reliable as possible. Enjoy the ultimate vanilla-style railway experience. π€οΈππ₯
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:IvidH7xV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VcPwJKGX:IvidH7xV"
}

