SpatialPackage

The SPATIALPACKAGE command exports and imports portable, versioned spatial-area packages. Version 3 transfers one or more zones: room coordinates, cells, active overlays, route-cell geometry, internal and selected cross-zone exits, zone geography and environment, tags, local covers, magic-resource state, and fully-contained area groups. Imports always create new zones and remap all room, cell, overlay, route, exit and area IDs. They never merge into or overwrite existing spatial content. Versions 1 and 2 packages remain importable. Files are read and written only inside the server's Spatial Packages directory. spatialpackage export zone <zone> <file> - exports a zone; the .fmsa.json suffix is optional spatialpackage export zones <file> <zone> [zone...] - exports multiple zones and links between them spatialpackage validate <file> <target shard> [new zone name] - preflights integrity and dependencies spatialpackage import <file> <target shard> confirm [new zone name] - creates the validated zone(s) You must be editing an under-design CELL PACKAGE to validate or import. A new-name override is only valid for a single-zone package. Quote multi-word zone, shard and file arguments where required. Spatial packages skip temporary cells such as dwellings and installed door items (while retaining the exit's door capability), but refuse hosted vehicle interiors, agriculture fields, persisted cell effects, surface liquids, and external fall destinations rather than silently losing those dependencies. Every deliberate omission is listed by export, validation and import.