GET YOUR BEARINGS
Plan your next NIMBY Rails session
This guide walks you through NIMBY Rails’ core systems, letting you measure the impact of design choices on cost, speed, and passenger satisfaction. By testing each tool in isolation, you can decide how deep to go into the sandbox without feeling overwhelmed.
01 / THE GUIDE
Map Scaling Test
Zoom in on a city and place a short commuter line using automatic aids. Then disable the aids and redraw the same segment, noting differences in track length and crossing count.
- Begin with a short regional segment to become familiar with the map’s scale before expanding globally.
- Zoom in on intersections to verify that tracks respect existing roads and streets.
02 / THE GUIDE
Signal Layout Comparison
Create two identical junctions—one with default signals, another with custom signals after disabling aids. Observe any changes in train throughput or bottlenecks.
- Use the automatic tools for early prototypes, then switch to manual mode to fine‑tune bottlenecks.
- After disabling aids, experiment with custom signal layouts for advanced traffic management.

03 / THE GUIDE
Train Type Trade‑off
Build parallel routes: a high‑speed line on a viaduct and a regional line on ground track. Record construction cost, average speed, and passenger rating for each.
- Pair high‑speed lines with viaducts to maintain speed over rough terrain.
- Use subways in dense urban areas to reduce surface disruption.
04 / THE GUIDE
Demand Timing Experiment
Run a line that serves a station in a different time zone. Track passenger numbers during the local night versus the partner zone’s day, adjusting service frequency as needed.
- Monitor peak‑hour demand to schedule extra services and avoid overcrowding.
- Adjust fares gradually to observe changes in passenger ratings and demand.
05 / THE GUIDE
Co‑op Coordination Drill
Start a multiplayer session with a partner. Divide the map into north and south halves, each building a network, and exchange updates every ten minutes to keep the overall system balanced.
- Assign each player a geographic sector to avoid overlapping work.
- Communicate schedule changes early to keep the shared network synchronized.




