> For the complete documentation index, see [llms.txt](https://docs.0resmon.org/0resmon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.0resmon.org/0resmon/0r-resources/0r-safezonecreator/editor.md).

# Editor

Open the menu with your configured command (default `/safezonecreator`). You need framework admin or the ACE permission from [Installation](/0resmon/0r-resources/0r-safezonecreator/installation.md).

***

## Workflow

1. **List** — search existing zones by id, name, or street.
2. **Create New** — set a unique id, display name, then place points.
3. **Edit** — load a zone, adjust points or settings, save.
4. **Delete** — removes the zone from `data/zones.json` and syncs all clients.

***

## Placing points (freecam)

From the zone form, start **Select Points** to enter freecam mode. Aim along the ground and click around the area you want protected — at least **three** points, in order along the border (no zig-zag through the middle).

| Input       | Action                              |
| ----------- | ----------------------------------- |
| Mouse       | Look around                         |
| WASD        | Move camera                         |
| Left click  | Add point                           |
| Right click | Undo last point                     |
| Q / E       | Raise / lower base Z for all points |
| X           | Increase zone thickness             |
| C           | Decrease thickness                  |
| Enter       | Finish and return to the form       |
| Backspace   | Cancel point mode                   |

After Enter, points and thickness are sent back to the UI. Review **Zone Settings**, optional blip and job whitelist, then **Save**.

{% hint style="warning" %}
If edges cross each other, the preview warns you and finish is blocked. Click corners in order around the perimeter, or undo and retry.
{% endhint %}

***

## Zone settings

Everything under **General Settings** and **Zone Settings** is stored per zone. A few practical combos:

* **Hospital** — invincible players, heal on enter, disable firearms, notification on.
* **PD lobby** — job whitelist for `police`, quiet footsteps, ghost mode off.
* **Dealership** — speed limit, lock doors, disable shooting, blip on.

**Thickness** controls how tall the polygon is vertically (default 15). Use Q/E in freecam if the zone feels too low or high on slopes.

***

## Job whitelist in the UI

1. Enable **Job Whitelist**.
2. Pick a job from the framework list (loaded from the server).
3. Set **Min Grade** — `0` means any grade for that job.
4. Add more rows as needed.

Whitelisted players still enter the zone; they simply ignore restrictions meant for civilians.

***

## Tips

* Use a **unique id** (e.g. `safezone_hospital`) — duplicates are rejected on create.
* Turn on **Show Zone Borders** while testing so you can see the shape from outside.
* Back up `data/zones.json` before bulk edits on a live server.
* After changing `config/main.lua`, restart `0r-safezonecreator` — zones themselves do not need a wipe.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.0resmon.org/0resmon/0r-resources/0r-safezonecreator/editor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.