Summary
Add official support for the Dungeon Crawling Add-on (v1.1.0) to the Lonelog plugin, enabling players to track room state during dungeon exploration sessions.
Motivation
Lonelog is built for narrative-driven solo play, but dungeon crawling introduces spatial and stateful tracking needs that the core notation doesn't fully address. Players exploring dungeons need to track:
- Which rooms have been entered, cleared, looted, or locked
- Connections between rooms (exits)
- A session-opening snapshot of all room states (Dungeon Status Block)
The existing L (location) tag handles simple spatial context, but not persistent room state that evolves over multiple scenes and sessions.
Proposed Solution
Implement support for the Dungeon Crawling Add-on notation as defined in the add-on spec (v1.1.0, requires Core Notation 3). This includes:
New Tag: R — Room
Format: R<ID><status>[<description>][exits DIR<R_ID>, ...]
Status values:
unexplored — Haven't entered yet
active — Currently exploring
cleared — Threats resolved
cleared, looted — Cleared and searched
locked — Cannot enter yet
trapped — Known hazard present
safe — Verified clear, usable as refuge
collapsed — No longer accessible
Directional shortcuts for exits: N, S, E, W, NE, NW, SE, SW, U (up), D (down)
Examples:
R3<cleared>
R3<cleared|library>
R3<cleared|library|exits WR1, NR4>
R3<looted> (inline status addition)
R3 (reference to established room)
New Structural Block: DUNGEON STATUS / DUNGEON STATUS
Session-opening snapshot of all room states. Opens at session start when resuming a dungeon crawl; replaced by an updated block next session.
DUNGEON STATUS
R1<cleared, looted|entry cave|exits NR2, ER3>
R2<cleared|guard room|exits SR1, WR5>
R3<active|library|exits WR1>
R4<unexplored>
R5<locked|heavy door|exits ER2>
DUNGEON STATUS
Cross-Add-on Interactions
The Dungeon Crawling Add-on is designed to work alongside:
- Combat Add-on —
R tag + COMBAT block inside a scene
- Resource Tracking Add-on —
R tag + Inv tags for torch/ration tracking
Alternatives Considered
- Using the existing
L location tag: Handles simple spatial context but lacks persistent status tracking and multi-state updates across scenes.
- Freeform prose notes: Inconsistent and hard to query or summarize at session start.
Additional Context
- Add-on version: v1.1.0
- Parent: Lonelog v1.3.0
- Requires: Core Notation 3
- License: CC BY-SA 4.0
- Originated from a community request by u/Jollto13 on r/SoloRoleplaying
- Design principle: Room tags track state, maps track space. The add-on is map-friendly by design — Room IDs connect the log to a visual map.
- Analog notebook support: Uses
--- DUNGEON STATUS --- / --- END STATUS --- dashed separators.
Summary
Add official support for the Dungeon Crawling Add-on (v1.1.0) to the Lonelog plugin, enabling players to track room state during dungeon exploration sessions.
Motivation
Lonelog is built for narrative-driven solo play, but dungeon crawling introduces spatial and stateful tracking needs that the core notation doesn't fully address. Players exploring dungeons need to track:
The existing
L(location) tag handles simple spatial context, but not persistent room state that evolves over multiple scenes and sessions.Proposed Solution
Implement support for the Dungeon Crawling Add-on notation as defined in the add-on spec (v1.1.0, requires Core Notation 3). This includes:
New Tag:
R— RoomFormat:
R<ID><status>[<description>][exits DIR<R_ID>, ...]Status values:
unexplored— Haven't entered yetactive— Currently exploringcleared— Threats resolvedcleared, looted— Cleared and searchedlocked— Cannot enter yettrapped— Known hazard presentsafe— Verified clear, usable as refugecollapsed— No longer accessibleDirectional shortcuts for exits:
N, S, E, W, NE, NW, SE, SW, U(up),D(down)Examples:
New Structural Block:
DUNGEON STATUS/DUNGEON STATUSSession-opening snapshot of all room states. Opens at session start when resuming a dungeon crawl; replaced by an updated block next session.
Cross-Add-on Interactions
The Dungeon Crawling Add-on is designed to work alongside:
Rtag +COMBATblock inside a sceneRtag +Invtags for torch/ration trackingAlternatives Considered
Llocation tag: Handles simple spatial context but lacks persistent status tracking and multi-state updates across scenes.Additional Context
--- DUNGEON STATUS ---/--- END STATUS ---dashed separators.