Map overview
map_overviewGet spatial orientation before per-tile reads: map extents, fort core, surface z, active z-levels, and ranked stairway runs—use it to choose which grids to pull.
Instructions
Cheap spatial orientation to run BEFORE any per-tile terrain read: map extents (x/y/z tile counts), the fort-core coordinate (the same 3D citizen centroid defenses() reports), surface_z_at_core — the surface z-level directly above the fort center, i.e. the highest open-to-sky ground tile in THAT ONE COLUMN, or null if the core is not under open sky (this is NOT geology()'s surface_z_max, which is the highest open-to-sky ground tile anywhere on the embark; on a sloped map the two legitimately differ by many z-levels, so pick the one you mean) — the z-levels that carry player activity (construction and pending digging, listed separately and as a union), and stairways collapsed to traversable single-column vertical runs (x, y, z_top, z_bottom); a run only spans levels that actually connect by DF stair rules, so a helical shaft splits into its climbable segments. The payload is fixed-size regardless of fort size: activity is a set of z-levels, never per-tile, and stair columns are RANKED BY HEIGHT (tallest run first) then capped, so when a fort exceeds the cap the tallest shafts survive and only trivial fragments are dropped (stair_columns_truncated flags the overflow; stair_columns_total gives the full count). Fog-of-war honest: undiscovered tiles never leak. Use it to decide which z-levels and area to pull grids for. Returns {"error":"no fort loaded"} if no fort is active.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||