Tags
Creators
Details
All versions
0.2.0-beta.2
Release
Create Train Physics Reloaded 0.2.0-beta.23 weeks ago 413
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
Fuel and Steam 'n' Rails
- Fixed liquid and solid fuels being consumed simultaneously.
- A train now uses only one fuel source per refueling cycle.
- When a suitable fluid is available, the first compatible Steam 'n' Rails fuel tank is used. Coal or other item-based fuel is consumed only when no suitable fluid is available.
- Multiple fuel tanks in different carriages no longer lose fuel simultaneously.
- A Create steam engine can now be placed directly on a Steam 'n' Rails fuel tank when building a locomotive, without requiring a temporary standard fluid tank.
- For multiplayer, it is recommended to disable
realisticTrainsin Steam 'n' Rails and control fuel requirements using this mod’srequireFuelsetting.
Electric Engines
- Electric engines from Create: Crafts & Additions, Create: Power Grid, and The Factory Must Grow no longer consume coal or liquid fuel.
- The
requireFuelsetting now applies only to steam engines and internal combustion engines. - Actual train power detection is still available only for Create: Electro Energetics. Electric engines from other add-ons are considered powered after the train is assembled because those mods do not provide a way to check their power network while the train is moving.
Reliability
- Added checks to ensure that only one fuel source is selected and that electric and fuel-powered engines operate independently.
- Saved trains now automatically update their engine classifications, including while the train is located in an unloaded chunk.
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:sOs1Eq2b:cKkqankx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sOs1Eq2b:cKkqankx"
}

