Keeping the Foundry Fed: Supply Routes in a Shared Simulation

The foundry stops just as your group begins building a second settlement. There is ore at the northern mine, coal beside the western forest, and three trucks circulating somewhere between them, yet the furnace inventory is empty. In a shared simulation game, this is a routing problem before it is a production problem. Consider a settlement with one mine, one coal yard, a central foundry, and an eastern construction depot. Planning its supply network means deciding what must move, how often it must arrive, and which player can change the plan without disrupting everyone else.

Start with the foundry’s consumption rather than the vehicles already available. Suppose it uses twelve units of ore and six units of coal per simulation minute while operating continuously. The construction depot needs eight finished beams per minute during the settlement expansion. Record those demands using the same time unit, then check whether the foundry’s output can satisfy construction. If it cannot, extra trucks will only deliver ingredients to a production bottleneck. This first calculation keeps the group from mistaking movement for useful throughput.

Next, measure a complete journey on each proposed route. A truck carrying sixty units of ore may look sufficient for five minutes of furnace demand, but its delivery rate depends on the entire cycle. If travel, loading, waiting, unloading, and returning take six minutes, that truck supplies only ten units per minute on average. It cannot sustain a twelve-unit requirement alone. Time several ordinary trips rather than one unusually clear run, and include the return leg even when the vehicle comes back empty.

Choose the road layout according to where delays actually occur. In this example, the northern mine and western coal yard both feed a narrow bridge outside the foundry. Sending every vehicle across it may be shorter on the map but slower in practice. Compare a direct bridge route with a longer southern approach, including the time vehicles spend yielding or queuing. Assigning ore to one entrance and coal to another can separate traffic streams. Avoid rebuilding the entire road network when a second approach would remove the specific conflict.

Decide whether each vehicle should serve one material or follow a mixed collection loop. A dedicated coal truck is easy to understand and adjust, while a truck that visits both the mine and coal yard may save vehicle capacity at low demand. However, the mixed loop also ties two supplies to the same delay: a queue at the mine postpones coal delivery as well. For the foundry’s essential inputs, use dedicated routes when capacity permits. Reserve mixed loops for small, predictable loads whose combined journey remains comfortably within the delivery interval.

Set loading rules to match the urgency of the cargo. Waiting until completely full can improve carrying efficiency, but it can also leave the foundry idle while a truck waits for the last few units. If the game supports departure conditions, test a minimum load paired with a maximum wait. For example, the coal truck might leave after collecting thirty units or waiting one simulation minute, whichever comes first. Check the resulting delivery rate afterward; a rule that sounds efficient may produce too many lightly loaded trips.

Place reserve stock where it protects production, not merely where storage space is cheap. A large ore pile at the mine does nothing for a furnace cut off by bridge congestion. Keeping thirty-six units beside the foundry would cover three minutes of ore consumption in this example. Choose that reserve against a plausible interruption, such as a delayed vehicle or temporary road closure. Give coal its own protected space so that an oversupply of ore cannot fill a shared warehouse and prevent the other essential ingredient from unloading.

Make route ownership visible before several players begin editing schedules. One player can oversee mine collection, another can manage foundry deliveries, and a third can coordinate outbound beams. Use clear route names, consistent vehicle groups, and a shared note explaining each route’s purpose. If a teammate uses the handle 1gom, a neutral assignment such as “1gom checks the eastern depot queue” identifies who will inspect that delivery point. The useful information is the assigned responsibility, supported by a clear handover when that player leaves.

Agree on a priority rule for competing deliveries. During the expansion, both housing construction and a replacement bridge may request beams from the eastern depot. If the bridge will restore a disrupted supply route, finishing it first may protect all later deliveries. Set that priority explicitly through destination limits, reserved cargo, or coordinated dispatch, depending on the game’s controls. Without a shared rule, two players can each redirect a truck toward a reasonable local goal while unintentionally starving the repair that the whole network needs.

Prepare a response for a blocked route before the blockage happens. Identify a usable detour, check whether its slopes or turns suit the assigned vehicles, and estimate its longer cycle time. If the southern road adds two minutes to every ore trip, the normal fleet may no longer meet furnace demand. Your contingency might combine the detour with temporarily reduced foundry output and a pause on nonessential construction. A backup route is only credible when the group understands what level of service it can maintain.

Test one change at a time and observe the network for several complete cycles. After adding an ore truck, inspect furnace stock, bridge queues, and unloading delays rather than simply watching the new vehicle move. Rising stock at the foundry suggests improved supply; a longer unloading queue may reveal that the receiving station has become the constraint. Keep a short change log so another player does not reverse an adjustment before its effects appear. When using a faster simulation speed, allow enough cycles to distinguish a persistent improvement from a lucky arrival pattern.

Recalculate the plan when the second settlement enters normal operation. Its construction demand may fall while maintenance and manufacturing demand increase, changing which routes deserve frequent service. Retire temporary collection loops, revise destination limits, and check whether previously empty return journeys can carry useful supplies without delaying essential inputs. Leave the group with a compact operating picture: expected consumption, assigned routes, reserve targets, and the response to a missed delivery. A dependable supply network is one teammates can inspect, understand, and adjust as the shared settlement changes.