Skip to main content
All Guides

Sessions and Lore

Sessions and Lore

This guide is a deep dive into two of LoreLedger's core features: lore entries and sessions. It is intended for GMs who want to understand the full range of options, but players will also find it useful for understanding how content is structured.


Lore entries

Lore entries are the building blocks of your world's shared knowledge. They describe the people, places, factions, objects, events, and other details that make your setting come alive.

Where entries live

Entries belong to a World. This means they are shared across all campaigns and tables within that world. A character entry created for one campaign is visible (subject to visibility rules) to all tables in the same world.

Entry types

Every entry has a type that describes what it represents:

TypeBest used forExamples
CharacterPeople and creaturesAn NPC tavern keeper, the villain, a player's backstory contact
LocationPlaces in the worldA city, a dungeon, a forest, a specific tavern
FactionGroups and organisationsA thieves' guild, a kingdom, a religious order
ItemNotable objectsA legendary sword, a cursed ring, a treasure map
EventThings that happenedA great war, a festival, a volcanic eruption
NoteEverything elseSetting rules, meta-game reminders, homebrew details

Entry types help with filtering and organisation. Choose the type that best fits the content.

Writing entries with Markdown

Entry bodies support Markdown formatting. You can use:

  • **bold** for bold text
  • *italic* for italic text
  • # Heading for headings
  • - item for bullet lists
  • 1. item for numbered lists
  • `code` for inline code
  • > quote for block quotes
  • --- for horizontal rules
  • [link text](url) for links

Markdown is rendered safely — any potentially harmful content is sanitised automatically.

Tags

Tags are free-form labels you can add to entries to help with filtering and discovery. You can use any tags you like — for example:

  • npc, pc, villain, ally
  • capital, dungeon, tavern
  • quest-hook, loot, historical
  • homebrew, official

On the entry list page, you can filter entries by tag. Tags are especially useful when you have many entries and want to find specific groups quickly.

Revision history

Every time you edit a lore entry, a new revision is saved. The revision captures the full state of the entry at that point — title, body, type, tags, and visibility.

To view revision history:

  1. Open an entry's detail page.
  2. Click History.
  3. Browse the list of revisions, each showing who edited it and when.

Revision history lets you see how an entry has evolved over time. This is useful for tracking changes in a collaborative setting or reviewing what was known at a particular point in the campaign.

Relationships

Relationships connect entries to each other. They are directional — you define a label for the connection from one entry to another.

Examples:

SourceRelationshipTarget
Captain VossMember ofThe Iron Guard
The Iron GuardBased inIronhaven
The Sunken CrownFound atThe Drowned Temple

To add a relationship:

  1. Open an entry's detail page.
  2. Scroll to the Relationships section.
  3. Choose a target entry from the dropdown (entries are grouped by type).
  4. Enter a relationship label.
  5. Click Add Relationship.

The reverse relationship is automatically shown on the target entry's detail page.

Notes:

  • You can create relationships to any entry in the same world.
  • You cannot create a relationship from an entry to itself.
  • Relationships respect visibility — if a player cannot see the target entry, the relationship is hidden from them.

Visibility on entries

Entries support all four visibility levels: All Members, Table Members, Organisation Staff, and GM Only. See Visibility and Spoilers for full details.

When visibility is set to Table Members, you can optionally scope the entry to a specific game table. This is useful in shared-world settings where different tables should see different content.


Sessions

Sessions represent individual play sessions at a game table. They are the bridge between your world's lore and actual campaign play.

Where sessions live

Sessions belong to a Game Table. Each session has a unique number within its table, making it easy to reference "Session 12" or "Session 3".

Session lifecycle

StatusWhen to use
PlannedYou have scheduled a session but it has not been played yet
CompletedThe session has been played
CancelledThe session was called off

Creating a session

  1. Navigate to your game table and click Sessions, then Create Session.
  2. Fill in:
    • Title — a short name for the session (e.g. "The Siege of Ironhaven")
    • Session number — automatically suggested as the next number, but you can change it. Must be unique within the table.
    • Status — Planned, Completed, or Cancelled
    • Scheduled date — when the session is planned for (optional)
    • Session date — when the session actually took place (optional)
    • Player summary — a recap of what happened, visible to all table members (Markdown)
    • GM notes — private notes for your eyes only (Markdown)
    • Visibility — who can see this session
  3. Click Create.

Player summary vs GM notes

These two fields serve very different purposes:

Player summary is meant to be a shared recap of the session. Write it as if you are telling the players what happened. It is visible to all table members (subject to the session's visibility setting). Good player summaries include:

  • What the party accomplished
  • Key NPCs encountered
  • Important discoveries
  • Where the session left off

GM notes are private to GMs and organisation staff. They are enforced at the server level — the data is never sent to players. Use them for:

  • Notes about what the party missed
  • Future plot hooks triggered by this session
  • Consequences of player actions
  • Prep notes for the next session
  • Reminders about NPC motivations

Attendance

GMs can track attendance for each session:

  1. Open a session's detail page.
  2. In the Attendance section, set each table member's status:
    • Present — they attended
    • Absent — they did not attend
    • Excused — they were absent with notice

Players can view attendance but cannot change it.

Linking sessions to lore entries

Sessions can be linked to lore entries to create a web of connections between what happened and the world's lore:

  1. On a session's detail page, scroll to Linked Entries.
  2. Choose an entry from the dropdown.
  3. Optionally add a context note (e.g. "First encounter with this NPC").
  4. Click Add Link.

Linked entries also appear on the entry's own detail page under Linked Sessions, showing which sessions reference the entry.

Session list

The session list page shows all sessions for a table, ordered by session number (most recent first). You can filter by status using the dropdown. Each card shows the session number, title, date, status, and a preview of the player summary.

Cloning a session

GMs can clone an existing session to quickly create a new one with similar content:

  1. On the session detail page, click the Clone button.
  2. This opens the "Create Session" form pre-filled with:
    • Title prefixed with "Copy of "
    • The next available session number
    • Status set to Planned
    • Dates cleared (so you can set new ones)
    • Summary, GM notes, and visibility copied from the source
  3. Adjust any fields as needed and click Create.

This is useful for recurring session formats or when you want to start a new session based on a template you have used before.

Editing and deleting sessions

  • Click Edit on a session's detail page to update any field.
  • Click Delete to permanently remove the session (GM or organisation staff only).

Campaign session timeline

The Campaign detail page includes a Session Timeline section that shows sessions from all tables in the campaign, ordered by date (most recent first). This gives GMs and players a unified view of campaign activity across tables.

The timeline respects visibility rules — players only see sessions they are allowed to view based on their table memberships and the session's visibility settings. The timeline supports load-more pagination, showing 10 sessions at a time.

Visibility on sessions

Sessions support all four visibility levels. See Visibility and Spoilers for details.


Related guides