If you like trains and Minecraft, you’ve probably seen the Rails of War Mod. You’ve downloaded it, started creating tracks, layouts, and stations. You’ve even had dreams of creating a regular freight and passenger service. The only problem; you can’t. With tankless tanks and random deaths, you sadly revert to Railcraft for your transport and freight needs.
Well, no more! I humbly present to you, the ROWAM-Rails of War Automation Module Mod 1.7.10, 1.7.2.
Ever wanted a scheduled train route but didn’t want to hire someone to work the locomotive for you? No problem. Want to restrict people’s locomotives to specific lines? We’ve got you covered. Need to transport your liquid in those snazzy-looking tank carts? Done. Tired of dying randomly while riding trains in survival? Not anymore with the ROWAM. The ROWAM can stop and start trains, control their speed, direct them on switches, and even allows for teleportation of locomotives and their riders using the Enhanced Portals 3 mod.
The signal block is the heart of the ROWAM. This block allows you to control the throttle of any locomotive through its GUI.
- Loco selector box. If left blank, the signal block will attempt to control any loco that passes it. Otherwise, the signal block only controls locos whose side text matches the text in the box. Ovs and Chers can have text affixed; it’s just not visible.
- Any loco with their throttle over this value will have their throttle set to the value in box 3
- The throttle value to set the loco to if it’s going faster than box 2.
- Any loco with their throttle under this value will have their throttle set to the value in box 5.
- The throttle value to set the loco to if it’s going slower than box 4.
- The throttle values in boxes 2 and 4 are based on speed, and ignore the direction the loco is traveling. This means that a loco with its throttle set to 50 in forwards is the same as one set to 50 in reverse. This allows you to run trains forwards and backwards on a line without multiple signal blocks.
- The throttle set values in boxes 3 and 5 are based on the current direction of the loco. A loco going backwards will always have its throttle set to the appropriate speed in reverse, while a loco going forward will always have its throttle set to the appropriate speed in forward. If you want to change the direction of the locomotive, just put in a negative sign.
- It is very possible to create a looping signal block if you set your values incorrectly. If your train starts shuddering, it’s a good bet you have a bad signal setting.
If the signal block is the heart of the ROWAM, the pointer block is the brain. Again, all options are set using its GUI.
- Loco selector box. If left blank the pointer won’t switch locos in regular mode. Otherwise, the pointer block only controls locos whose side text matches the text in the box. Ovs and Chers can have text affixed; it’s just not visible.
- Any loco that has a label matching box 1 will be switched in this direction. If the pointer block is in spring mode, this controls the set position of the spring. Main line will always be the route that’s straight through the switch, while siding is the branch line.
- Controls the switching behavior of non-matching locos. Non-matching locos can be set to go in the opposite direction of matching locos, or just be ignored. This allows for ‘locked’ switches that only let certain lines through.
- Enables redstone mode. In this mode, the pointer block switches any nearby pointers based on the redstone signal it receives.
- Enables spring mode. In this mode the switch will keep itself locked in the position set in box 2, even if a loco runs through it.
The station block allows for the creation of stops along your rail route. It stops trains, applies brakes, loads entities, schedules departures, and will even blow a train’s whistle when it arrives. If it is holding a loco, it will output a redstone signal through a comparator. Like the previous blocks, all settings are in the GUI. The buttons on the top of the GUI switch between loco and freight settings, with the loco settings dealing with station events, and the freight settings dealing with entity loading and unloading.
- If left blank, the station block will attempt to stop any loco with a throttle of 0 that passes it. Otherwise, the sation block will only stop a loco with a throttle of 0 whose side text matches the text in the box. Ovs and Chers can have text affixed; it’s just not visible.
- Changes the event that will launch a stopped loco. If the station is in time delay mode, it will launch the loco after a specific number of ticks has passed. If set to scheduled mode, it will launch the loco at a specific time. If set to redstone mode, the station block will launch a loco when it receives a redstone signal.
- If the station is in time delay mode, this box is the number of ticks (1/20 of a second) to wait before launching the held loco. If the station is in scheduled mode this is the time (standard Minecraft times and time format) at which to launch the held loco.
- What to set the departing loco’s throttle to. Negative values make the loco depart in reverse.
- When to sound a loco’s whistle. This can be during arrival, departure, both, or neither.
- Pitch and volume of the whistle. A higher volume extends the range of the whistle, but does not make it louder.
- Entity to load into train just prior to leaving the station.
- Stock to load entity into. The entity must be near the stock prior to departure for them to be loaded.
- Side to load the entity from. ‘Both’ loads from both the left and right sides of the stock. ‘Left’ and ‘Right’ are determined by the direction the loco that is stopped by the station block is facing.
- Entity to unload from the train. This happens when the train is stopped by the station block during arrival.
- Stock to unload entities from.
- Side to unload the entity to. ‘Left’ and ‘Right’ are determined by the direction the loco that is stopped by the station block is facing.
Note that entities must match the entity selector and be near the loading point of a cart during departure to be loaded. This can be a bit of a problem if your animals or villagers tend to crowd around each other.
The tank block puts your tank carts to use for you, allowing them to hold liquids. Placing a tank block next to any forge-compatible tank block will transfer the tank’s fluid into nearby tank cars. Right-clicking the tank block will toggle it from drain to fill mode. If provided with a redstone signal, the tank block will stop working. Additionally, any tank block that’s currently filling or draining a tank cart will output a redstone signal. To make sure you don’t put lava in your water tank cart and end up hauling obsidian, the tank block assigns each new tank cart a color which reflects its contents. Any newly-placed tank cart that’s about to accept a liquid will have its color changed to reflect that liquid, and from then on it will only work with that liquid. Changing a tank cart’s color with a dye will cause it to work that type of liquid, permitting re-use of carts. Currently, only water, lava, oil, and fuel are compatible with the tank block, due to the limited static NBT data of the tank carts; other fluids can be added to the code if desired.
The fueling block allows you to keep your trains running during long hauls by refueling any nearby locomotives and tenders. It pulls coal from an adjacent chest, and outputs a redstone signal while it’s fueling. It will only fuel a locomotive to its max fuel value, after which it stops outputting redstone. Because of this it can be used in conjunction with a signal block and station block to create automatic refueling points on your railway.
Note that due to a bug with the way ROW has the OV’s tender coded the fueling block may leave dummy coal pieces lying under the tender. These don’t come from the coal in the chest, and cannot be picked up by players.
The detector block is appropriately named, as it outputs a redstone signal when a locomotive or cart is nearby. While it doesn’t do anything spectacular, you can combine this function with pointer blocks to switch carts or with other mods to create a locomotive detection network.
The ROWAM does a few other things under the hood automatically. This includes chukloading, fall damage removal, and player rotation. Specifically, ROWAM does these things every tick:
- Loads a 3×3 chunk around any ROW stock.
- Removes all fall damage from ROW stock, eliminating the random deaths.
- Causes all ROW stock with portal cooldowns to update correctly, enabling you to send them through portals.
- Fixes the position of all riding entities so they don’t have their feet through the floor.
- If a player is riding ROW stock, and that stock is turning, they are rotated the same amount as that stock.
ROWAM Rails of War Automation Module Mod Installation
- First you need download and install Minecraft Forge.
- Then download this Minecraft mod file at link below.
- Go to %appdata%. It can also be found by searching for “%appdata%” in your start menu.
- Go to .minecraft/mods folder.
- If the “mods” folder does’nt exist in your PC, you’ll need create one.
- Then drag and drop the downloaded .jar (or .zip) file into mods folder.