All versions
0.2.1+neoforge-mc1.21.1
Release
Steam 'n' Rails Neoforge 0.2.1+neoforge-mc1.21.1last month 197.8K
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
What's Changed
- fix: connect copycat headstock textures across buffer/coupling styles (#283) by @gblfxt in https://github.com/Porters-of-Railways/Railway-1.21.1/pull/295
- feat: recognize conventional c:fuel fluids as train fuel (#281) by @gblfxt in https://github.com/Porters-of-Railways/Railway-1.21.1/pull/294
- fix: correct phantom-track signal marker orientation (#242) by @gblfxt in https://github.com/Porters-of-Railways/Railway-1.21.1/pull/293
- Fix fuel tank rendering by generating its blockstate on NeoForge (#287) by @gblfxt in https://github.com/Porters-of-Railways/Railway-1.21.1/pull/296
- Added Bulgarian translation (bg_bg.json) by @Programstor in https://github.com/Porters-of-Railways/Railway-1.21.1/pull/286
- fix: apply data fixers to Create schematics by @gblfxt in https://github.com/Porters-of-Railways/Railway-1.21.1/pull/297
- fix: fixed crashes regarding track buffers by @PoppyBlossom in https://github.com/Porters-of-Railways/Railway-1.21.1/commit/0ad5d6f6fd39508994ca14e34630e853da39ff3e
- fix: use c: rod tags instead of dead forge: tags on TFC tracks by @gblfxt in https://github.com/Porters-of-Railways/Railway-1.21.1/pull/299
- fix: mitigate NVIDIA Linux shutdown hang by force-exiting wedged client JVM (#267) by @gblfxt in https://github.com/Porters-of-Railways/Railway-1.21.1/pull/292
New Contributors
- @Programstor made their first contribution in https://github.com/Porters-of-Railways/Railway-1.21.1/pull/286
Full Changelog: https://github.com/Porters-of-Railways/Railway-1.21.1/compare/v0.2.0...v0.2.1
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:L3Jv0QZI:HOPX5oro"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:L3Jv0QZI:HOPX5oro"
}


