Rooftop route planning
Compare anchor access, height gain, landing safety and the street fallback before committing to a swing line.
Operational objective
A rooftop line looks like the fast answer because it ignores intersections. What it actually does is trade a known cost — traffic — for four unknown ones: whether the anchor is there, whether the height is recoverable, whether the landing is survivable, and whether the street below can still be reached. This page turns those four into checks you run before committing, not after.
Decision route
- Read the line backwards from the target roof. The question is not "can I get up" but "does this specific roof connect to anything".
- Confirm anchors before height. Gaining altitude with nothing to swing from at the top converts a route into a climb down.
- Treat height as banked, not spent. Altitude gained early is usable later only if the line between the two roofs does not force you to give it back.
- Pick the landing before the jump. A landing you have not looked at is the part of the route most likely to end it.
- Keep the street reachable at two points, not one. A single descent is a plan; two are a route you can still abort from halfway.
Failure review
- Planning the climb and calling it a route. Getting up is the cheapest part of any rooftop line.
- Using a rooftop line to carry something the street was going to carry for you.
- Reading a roof gap as jumpable because a similar one was, in a district built to a different scale.
!
Unreleased: swing and grapple mechanics, whether anchors are placed by hand or generated, fall damage, stamina, and how roof density differs between districts. Treat the checks above as a planning order, not as confirmed physics.