- Plan B: Terraform bridges are not a manually placed construction option in the current version.
- Road routing currently works best when you plan around terrain, water, and transport bottlenecks.
- Rail crossings need extra visual planning because roads and rails can overlap awkwardly.
- Developer notes describe possible automatic bridges over limited water depth, not ocean crossings.
- Best workaround: use compact road networks, short crossings, and separate transport lanes.
Plan B: Terraform Bridges: Current Status
Plan B: Terraform bridges work differently from a standard building you place from the construction menu: roads and rails handle limited water crossings automatically, while large ocean crossings remain unavailable. That distinction matters when designing a planetary transport network.
The practical takeaway is simple: do not base an entire logistics chain on bridge construction until the feature is visibly available in your build. Instead, create routes that can function without direct water crossings. Use the terrain as a planning constraint, then reserve short crossings for areas where an automatic bridge or future transport update may eventually help.
Video Highlights:
- Planet-wide road planning across a terraformed hex-grid world
- Long-distance roads connecting industrial and city regions
- Transport bottlenecks caused by inefficient route layouts
- Practical examples of roads, trucks, depots, and supply centers
The current bridge question is closely tied to how roads and rails interact. A linked Steam Community discussion about bridges in Plan B: Terraform records concerns about missing bridges, tunnels, and crossings. The discussion also notes that vehicles can pass through one another at intersections, which reduces the immediate functional need for collision-safe overpasses but does not solve the visual problem.
| Feature | Practical status | Planning advice |
|---|---|---|
| Road over shallow water | Not a selectable building | Leave room for the automatic crossing |
| Road over deep ocean | Described as unlikely in the developer note | Route around major ocean gaps |
| Rail over water | Handled automatically | Keep rail corridors separate from road corridors |
| Tunnels through mountains | Not a placeable option | Use mountain edges when direct crossings are unavailable |
| Road and rail intersections | Functionally possible but visually awkward | Separate lanes and avoid dense crossings |
Do not assume that every water tile supports a bridge. Test the route in your current build before committing production resources, roads, or rail infrastructure.
How to Route Roads Without Bridges
When bridges are unavailable, the strongest approach is to design roads around transport needs rather than drawing the shortest possible line. In a game built around a spherical planet and hexagonal tiles, the visually shortest route is not always the most reliable route. Mountains, polar terrain, production distance, and road availability can all affect the final design.
Roads connect road stops, and trucks move resources between production chains, depots, and supply centers. A road that looks efficient may still create a queue if too many trucks share one stop. Before expanding across water, make sure the road is solving a real logistics problem.
Identify the Transport Need
Start by locating the resource, factory, depot, or city that requires a connection. Confirm the destination's demand before building a long route. Supply centers should be placed close enough to the city network to support growth without creating unnecessary transport distance.
Trace a Land-Based Route
Look for a path that follows connected land tiles. A longer route around a bay or inland sea may be more dependable than a direct path that depends on an unavailable bridge.
Place Road Stops at Both Ends
Build a road stop at the origin and another at the destination. Configure the truck route explicitly so the correct resource moves in the intended direction.
Add Trucks Gradually
Begin with a small truck group and watch loading, travel, and unloading behavior. Add vehicles only when production or city demand justifies the increase.
Review the Route After Expansion
Cities and factories can expand the network's demand. Recheck the road after adding supply centers, new depots, or upgraded resources such as reinforced concrete and oxygen.
A land detour is especially useful early in a colony. Roads require concrete, and concrete production depends on a functioning chain that can include sulfur extraction, factories, depots, road stops, and assembly plants. Spending roads on a decorative shortcut can delay the infrastructure needed for population growth.
| Route type | Strength | Weakness | Best use |
|---|---|---|---|
| Coastal detour | Avoids water crossing uncertainty | Longer travel distance | Early industrial links |
| Inland loop | Stable land connection | Uses more road tiles | High-value city supply routes |
| Short water gap | Potentially efficient if supported | Feature availability may vary | Experimental late routes |
| Mountain-edge route | Avoids blocked terrain | Can become winding | Mixed industrial regions |
| Planetary loop | Connects distant regions | Expensive and slow to build | Long-term transport backbone |
Build the shortest reliable route, not necessarily the shortest visible route. A dependable land loop is usually easier to expand than a direct path that depends on automatic water crossings.
Roads, Rails, and Crossing Layouts
Road and rail networks should be planned as separate systems whenever possible. The available discussion specifically describes roads and rails looking unattractive when placed together, particularly where crossings or shared terrain create broken-looking textures. Even if vehicles can pass through one another, visual clutter can make a mature colony difficult to read.
A good layout gives each transport mode its own corridor. Roads can serve trucks carrying concrete, oxygen, mechanical parts, and other city supplies. Rail should be reserved for high-volume routes once the network justifies a more permanent connection. Keeping the systems apart also makes it easier to diagnose a stalled route.
Road Corridor
- Flexible truck delivery
- Easy to extend
- Strong for city supplies
Rail Corridor
- Suitable for major routes
- Requires more planning
- Keep crossings visually clear
Mountain Route
- Uses terrain edges
- Avoids blocked tiles
- May need extra distance
Water Detour
- Does not rely on bridges
- Safe for early planning
- Costs additional road tiles
Use a simple hierarchy when expanding:
- Local roads should connect nearby extractors, factories, and depots.
- Regional roads should connect production zones with supply centers.
- Long-distance routes should move high-value resources between separated regions.
- Rail corridors should avoid unnecessary intersections with dense truck traffic.
- Potential bridge locations should remain open enough for future redesign.
| Network problem | Likely cause | Recommended response |
|---|---|---|
| Trucks wait in a queue | Too many vehicles share one stop | Reduce trucks or split the route |
| Factory lacks input | Depot or route is disconnected | Check origin, destination, and resource setting |
| City growth stalls | Supply center lacks required materials | Verify concrete, oxygen, or upgraded supply inputs |
| Road looks broken near rail | Overlapping transport corridors | Move roads and rails into parallel corridors |
| Route crosses blocked terrain | Mountain or water limitation | Use a detour and preserve room for upgrades |
Treat roads and rails as readable corridors. Even when intersections are functional, separating transport modes makes resource flow easier to inspect and future bridge changes easier to apply.
Bridge-Ready Planetary Planning
A bridge-ready layout does not require bridges to work today. It means leaving enough flexibility to add or replace crossings later without rebuilding the entire colony. This is important on a planet where cities expand, production chains become more complex, and roads can eventually span large portions of the globe.
Start by identifying natural crossing points. A narrow water gap between two developed regions is a better candidate than a wide ocean route. Keep industrial buildings slightly away from the shoreline when possible, and avoid placing a depot directly where a future road or rail crossing may need to pass.
Resource chains also influence bridge planning. Iron supports steel production, steel supports mechanical parts, and mechanical parts can support trucks and other buildings. Sulfur and concrete become important for road construction and city supply. Aluminum, atmospheric extraction, oxygen, and reinforced concrete extend the network into later population milestones.
| Planning stage | Main transport priority | Bridge preparation |
|---|---|---|
| Early colony | Iron, steel, extractors | Use compact local roads |
| First city growth | Concrete and supply centers | Reserve a clear city approach |
| Regional expansion | Mechanical parts and trucks | Separate production and delivery lanes |
| Larger population | Oxygen and reinforced concrete | Upgrade high-demand corridors |
| Planetary network | Roads, rail, and multiple cities | Keep narrow crossing points available |
Use these design rules when preparing a route:
- Place production clusters on connected land whenever possible.
- Keep road stops away from tight corners and crowded factory blocks.
- Avoid sending every resource through one central depot.
- Use separate entry and exit paths for large supply centers.
- Mark narrow water gaps as possible future crossing locations.
- Record which routes are essential before deleting or rerouting them.
- Test one transport change at a time so failures are easy to identify.
Bridge-Ready Network Checklist:
- Confirm every essential city supply route works without a bridge
- Keep road and rail corridors visually separate
- Reserve narrow water gaps for possible future crossings
- Avoid placing critical depots on likely bridge approaches
- Test truck quantities before expanding a long-distance route
A network that already works with land detours can benefit from bridges later, but it will not collapse if bridge support changes or remains limited.
Troubleshooting Water Crossings
The most common mistake is treating a missing bridge as the only problem. In many cases, the real issue is an incomplete logistics chain. A road may be present while the road stops are not configured, trucks may exist without a valid origin, or the destination may be waiting for a different resource than the one being delivered.
Check the route in this order:
- Confirm the producer is making the required material.
- Confirm a depot stores or receives that material.
- Confirm both road stops are connected to the intended road.
- Confirm the truck route has the correct origin and destination.
- Confirm the destination actually consumes the resource.
- Reduce traffic if trucks are waiting without unloading.
The same logic applies to a route that appears to cross water. First verify whether the game recognizes the connection. If the road cannot be completed, do not continue placing infrastructure blindly. Delete the failed segment if necessary, then build a land-based detour.
The developer discussion linked above describes a possible automatic bridge behavior for limited water depth and a likely restriction on crossing large oceans. Because that statement is not a placement tutorial or a confirmed feature list, use it as planning context rather than a guarantee. Check the current game build before spending a large road stockpile on a water route.
Q: Can you build bridges in Plan B: Terraform?
Plan B: Terraform does not include a standard, manually placed bridge building option. Roads and rails cross limited water automatically, while large ocean crossings remain unavailable.
Q: What should I do if my road reaches water?
Try a land-based detour around the water. If the current build recognizes the crossing, test it with a short route before committing a major planetary network.
Q: Are tunnels available for mountain routes?
Tunnels are not a dedicated build option in the current version. Mountain-edge detours are the safest planning option until a future update adds a dedicated tunnel or automatic terrain solution.
Q: Should roads and rails share the same crossing?
Avoid combining them when possible. Shared crossings can look awkward and make troubleshooting harder, so separate corridors are easier to manage.
Save or test a small section first. A long route can consume substantial concrete and truck capacity, and a bridge assumption may leave the entire chain disconnected.