Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 years ago
Updated yesterday
All versions
2.0-snapshot.3
Beta
RailOptimization 2.0-snapshot 32 weeks ago 155
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
Platforms
Fabric
Quilt
Supported environments
Server-side
Singleplayer
Changes
RailOptimization v2.0-snapshot 3
This snapshot brings RailOptimization to NeoForge, adds persistent configuration, and further reduces powered and activator rail signal-search overhead while preserving vanilla behavior.
✨ What's New
- Added NeoForge support for Minecraft 26.1.x
- Runtime settings are now saved to
config/railoptimization.jsonand persist across game or server restarts - Added
/railoptimization reloadto apply configuration-file changes without restarting - Fabric and NeoForge share the same optimization engine, commands, and configuration behavior
- Configuration writes are handled asynchronously and replaced atomically
🚀 Performance
- Reused block states already read during direct-power checks, avoiding duplicate world lookups on unsuccessful rail signal searches
- Streamlined direct-signal direction checks without changing Minecraft's signal observation order
- In balanced local measurements, complete no-signal searches were about 10% faster at the default power range and 13% faster at
powerLimit=64, with successful and early-exit paths effectively unchanged - No additional per-update allocation was introduced
⚠️ Snapshot Notes
- This is a snapshot intended for testing before the final v2.0 release
- Snapshot builds are only provided for selected Minecraft versions; all supported versions will be updated with the final release
- There are no intentional gameplay behavior changes; vanilla behavior and the default rail power range remain unchanged
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| railoptimization-2.0-snapshot.3+mc26.1.2-fabric-sources.jar | Sources jar | 74.94 KiB |
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:QSvN5pBU:BnDNNkIj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QSvN5pBU:BnDNNkIj"
}

