## Example

```json
{
  "unassignedAreas": {
    "Old%20Mill/Quiet%20Hollow": {
      "description": "A shaded bend in the river where the mill wheel has not turned in years.",
      "paths": [],
      "visualTags": [
        "river",
        "abandoned"
      ]
    }
  }
}
```

## Fields

### description

What the area is, in the same terms a [location](/world/locations)'s own `areas` entry uses. Required.

### paths

The area keys this one connects to. Required, and an empty array is valid — an area waiting for a location usually has nowhere to lead yet.

### visualTags

Short descriptors the image generator reads. Optional.

### images.establishingShot

The area's establishing shot. Optional as a whole, but once it is present the `crop` is required, and that crop needs a `focus` of `x` and `y` plus a `zoom`. `imageUrl` is the optional part.

## How entries get here

An entry appears when an area stops belonging to a location, such as when it is detached from it in Studio. The area keeps its own content; only its place in the map is gone.

Studio writes the entry and its key for you, so this is not a section you author from scratch.

## Every entry blocks save and publish

An area here has no place on the map, so the world will not save or publish while the section holds anything. Give each entry a location, or delete it.

This is the one section whose contents are an error by definition: an empty `unassignedAreas` is the healthy state, and a populated one is a draft midway through a change.