Doors between places¶
Nerthus.Core (until cutover). This page describes the frozen system that runs today and is deleted at cutover. Replaced by: not yet written.
A door (@drzwi) is a passage between two places. Most doors you will never write: the tool derives them from fetched game logs and writes them for you. The ones you do write follow a different rule, and mixing the two up is the mistake this page exists to prevent.
Read both halves before you write a @drzwi line.
The line¶
A @drzwi line sits on a Lokacja block and on a Mapa block alike - on a map block it records that two game maps connect:
The value is the name of the place on the other side. The (auto) marker is the tool's signature, and it changes everything about how the line behaves.
Doors the tool derives from logs¶
When a fetched game log shows the party walking straight out of one place into another, the tool records that pair as a door. It writes the line on both places' blocks, and marks each line (auto):
The (auto) marker means the tool wrote this line and will write it again. Derived doors come out of fetched session logs, so more of them appear as you fetch more - see Link session logs.
You have two answers to a derived door.
Accept it¶
Delete the (auto) marker on both lines. The door is now yours and the tool stops touching it.
Reject it¶
Close the line's date range on both blocks:
The (:2026-07) suffix closes the value at July 2026. Closing is a permanent rejection: the tool will not re-add that door, however many times it reads the same logs again.
Do not delete a derived door - close it
Deleting the two (auto) lines does not reject the door. The log evidence is still in the archive, so the next rebuild writes the pair straight back. Closing the range is the gesture that sticks.
Doors you write by hand¶
A hand-written door is written on one block only - the block you typed it into. The tool does not mirror it onto the other place for you.
One @drzwi line is a one-way door
Doors are two-way in the world, but writing one @drzwi line does not make the tool write the matching one. Worse, the tool now treats that pair as already handled, so it will never fill in the missing side. If you want a passage traversable both ways, write it on both places' blocks yourself.
So a passage between Rezydencja Tussal and Ogród Tussala is two lines, in two blocks:
Once both lines are in, the door is safe. Rebuilding the location list never overwrites a hand-written door, never removes it, and never marks it (auto).
The two rules side by side¶
Derived ((auto)) |
Hand-written | |
|---|---|---|
| Who wrote it | the tool, from a fetched log | you |
| How many sides | both, always | only the one you typed |
| To keep it | delete (auto) on both lines |
nothing - it already sticks |
| To remove it | close the range on both lines | delete the line |
| Survives a rebuild | it is rewritten unless closed | untouched either way |
The asymmetry is worth stating plainly: the tool writes both sides and you write one. Every hand-written door needs a second line from you.
A door is not the tree¶
@drzwi and @lokacja answer different questions and neither implies the other.
@lokacjais containment: the garden is inside the residence. It builds the location tree and it decides paths.@drzwiis a passage: you can walk from the residence into the garden. It builds the traversal graph and it decides nothing about paths.
Two places can be connected by a door without either containing the other - Thuzal and Ithan are separate cities with a road between them. And a place can sit inside its parent with no door at all, when there is no walkable passage worth recording.
Related¶
- Locations and maps - the location tree, and
LokacjaagainstMapa - Link session logs - fetching the game logs derived doors come from
- Add and edit entities - dated ranges and the close-and-append gesture