Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 months ago
Updated 2 weeks ago
All versions
SNR.FLY-STABLE-1.4
Release
SNR.FLY-STABLE-1.42 weeks ago 3,448
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
- Fix mounted conductor toolboxes using an incorrect Create Fly block type.
- Resolve bogey default styles after registration instead of retaining Create's initial standard style.
- Avoid the conductor chunk-tracking hook when Very Many Players is installed.
- Resolve whistle train names from the client railway manager and add a compact tooltip option.
- Release railway graph points when their blocks are moved into contraptions.
- Drop track casing with broken tracks and render casing with correct normals when Flywheel instancing is disabled.
- Use specialized narrow and wide track blocks, restore mixed-material crossings, and apply gauge-specific curve rules.
- Reject existing and prospective crossings at curve endpoints before consuming items or placing pavement, and return casing after successful crossing conversion.
- Remove collided handcars from the railway graph and return their items.
- Give handcars a distance-attenuated cog sound without steam sounds or smoke, and suppress invisible bogey effects.
- Hide device overlays on phantom tracks and restore them on generic crossings.
- Set the line width when drawing custom block outlines.
- Add the station reservation toggle with persistence, navigation and network synchronization; increase the network protocol to 16.
- Add empyreal, maple and pine Biomes O' Plenty tracks at all three gauges and refresh mahogany, redwood and umbran textures.
- Update translations and add Italian.
- Check that the runtime and archive versions match before compiling.
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:f20AygJv:TOvV3nUU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:f20AygJv:TOvV3nUU"
}

