Every cable is real
Cabling isn't a menu action in Uptime. You pull it off the spool, find the port, and watch it lay across the floor. And the link it makes does real work in the simulation.
In most tycoon games, “connect the network” is a button. In Uptime it’s a job you do with your hands.
You pull the cable off the spool, walk it to the rack, find the right port, and seat it with a click. It lays across the floor with real sag, and there’s a bend radius you can get wrong. It’s meant to feel the way Factorio makes a belt feel good: tactile, deliberate, yours.
The link does real work
What makes it more than set dressing is what happens underneath. Every port and every cable is a typed entity in a deterministic engine. A cable only carries traffic when both ends are seated in compatible ports; pull one end and the thing on the other side actually goes dark, because reachability runs host → switch → demarc → uplink and the chain just lost a hop.
Get clever and it pushes back. Bond several links into a LAG and the bandwidth budget adds up the way it should. Cable a redundant path the wrong way and spanning tree either saves you (electing a root bridge, blocking the loop) or, if you got it wrong, the whole floor drowns in a broadcast storm.
Same layout, same outcome
Because the engine is deterministic, a given layout behaves the same way every single run. That’s not a detail for us; it’s the whole reason an SRE can trust what they’re looking at. When a link saturates, it’s because the math says it saturated. When a rack goes dark, a fault domain you didn’t think about turned out to be a single point of failure.
Come run a cable with us. The Discord is where the wiring arguments happen.