Skip to content

Regions

Nerthus.Core (until cutover). This page describes the frozen system that runs today and is deleted at cutover. Replaced by: not yet written.

A region is a named group of places. The location tree says what contains what; a region says what belongs together. Places sitting in different parts of the tree can share one region, and a border can move without any folder moving.

This page shows how to create a region, how to put a place in one, and how to record a border that moved.

Create the region

A region gets its own block, under its own ## Region section, and you create it the way you create any entity - by writing the block:

## Region

### Południowa Elancja
- @typ: Region
- @status: Aktywny

That is a complete region. It needs nothing else, because a region's block never lists its members.

Membership is one line on the place

To put a place in a region, add one dated @region line to the place's block - not to the region's:

### Racicowy Matecznik
- @typ: Lokacja
- @region: Południowa Elancja (2020-04:)

The open range means "from April 2020 onward". Name the region exactly as its heading spells it, diacritics included - a @region line naming a region that has no block is reported to you, not quietly ignored.

The direction is deliberate. A region can gain a hundred places over ten years without its own block ever being edited, and looking at a place tells you which regions it has belonged to, and when.

A border that moves is close-and-append

Never overwrite. When the border moved in July 2026:

- @region: Południowa Elancja (2020-04:2026-06)
- @region: Elancja (2026-07:)

Both lines stay. The record keeps where the place belonged before the border moved, so "which region was Racicowy Matecznik in when that session happened?" has an answer.

This is the same gesture as moving an NPC between cities - Add and edit entities owns it.

A region can sit inside a bigger region

The same one-line gesture, written on the smaller region's block:

### Południowa Elancja
- @typ: Region
- @region: Elancja

A region that contains itself, directly or around a loop, is an error the tool reports - the same rule as a place that contains itself in the tree.

What a region is not

Each of these is a real mistake, and each has bitten somebody:

  • Not a map. A region groups places (Lokacja), never game maps (Mapa).
  • Not the folder tree. Putting a place in a region does not move it - its @lokacja parent, its path, and its session copies all stay exactly as they were. A top-level folder like Reszta Świata is a folder; a region is always its own block.
  • Not a parent. A place still needs its @lokacja line; @region never replaces it.
  • Not somewhere sessions land. Sessions are copied to places, never to regions. A region has no @plik and gets no copies.

The short version: @lokacja is where a place is, @region is what it counts as. A place has exactly one parent and any number of region memberships over time.

Retire a region

Same gesture as anything else - see Add and edit entities. Retiring a region does not touch the places that named it; their @region lines stay on the record, which is the point.

If the region stopped existing because its border moved, close each member's @region line as well, so the places say when they left.