map-api

Part of the host contract in host.wit. Host-owned, read-only queries over the loaded map. One function today; the interface exists so map facts have a home that is not the entity verbs.

Imported by the server world (server-mod) only.

`spawn-points`

record spawn-point { position: vec3, yaw: f32 }

spawn-points: async func() -> list<spawn-point>;

What the loaded map suggests, not where anyone will stand: the session’s gamemode decides that and is free to ignore every one of these. Yaw is in radians, feeding straight back into entity.spawn. Never empty: a map declaring none yields the engine’s own fallback point.

Authoring maps — declaring spawn points
spawn — the host’s own placement of arrivals
entity — spawning at a point