Skip to content

The activity feed

The activity log is the GM’s record of everything that happens at the table: combat turns, token movements, dice rolls, card plays, targeting, resolutions, conditions, resources, fog, and every change made while building the map. It is yours alone. Your players see the game log, the record of what happened that the whole table keeps, and the moment-to-moment news in the feed at the bottom left of the map.

Where What it is Who sees it
Activity (this page) Everything, as it happens, with rewind The GM
Game Log What happened: rolls, card plays, outcomes and notes, kept for the campaign Everyone in the room
The feed at the bottom left of the map What’s happening now: rolls, news, and anything waiting on you Each person, for what concerns them

For the slash command input bar at the bottom of the log, see the Slash Commands guide.

The activity log lives in the Log tab of the Table panel, at the Play table, on its Activity page. The Log key on the quick bar at the bottom of the map opens it too, and carries a count of entries that arrived while the tab wasn’t showing. Players and observers have no Activity page: their Log tab is the game log.

Each entry in the feed represents a gameplay event. Entries appear in real time as the session progresses. Each one shows:

  • Category icon — a colour-coded icon indicating the type of event
  • Message — a human-readable summary (for example, “Goblin’s turn”, “Combat started” or “Mira Halloway’s HP −5 21 → 16”)
  • Detail — optional extra context (for example, “Round 3” or a list of changed fields)
  • Version number — the event version, visible on hover (used for rewind/revert)
  • Timestamp — the time the event occurred (HH:MM:SS format)
Icon colour Category Example events
Your palette’s accent Combat Combat started/ended, combatant joined/removed, round changes, turn advances
Your palette’s accent Card A card played, shown as the card with every step underneath: how it was aimed, the template it placed, choices made along the way such as a spell slot, each roll, and what it did
Grey Token Token added/removed, moved, updated, resized, a door opened or closed
Amber Fog Fog revealed, reset, visibility changed, strokes painted/erased
Green Dice Every roll at the table, yours and your players’
Your palette’s second colour Targeting Targeting started, updated, confirmed, cancelled
Violet Resolution Resolution enqueued, response requested/submitted, resolved, cancelled
Calm Status Conditions applied, ticked, expired and removed; resources and hit points changed, with both values
Grey System/Command Building the map (walls, lights, grid, tiles, effects, terrain, pins, levels), slash command feedback

Nothing is left out. A burst of the same thing — four quick nudges to one token’s hit points, a run of fog strokes — folds into one line that says how many times it happened (“· 4 times”).

The log keeps the most recent 500 entries, from when you opened the table. It stays put while you close and reopen the Table panel. After a reload it starts again from that moment; the full history is kept on the server, which is what rewind reads.

The feed resolves token and combatant names automatically:

  • Token events show the token’s display name (for example, “Goblin” instead of a raw ID)
  • Combat events cross-reference the combatant’s token to show a friendly name
  • Dice rolls show the roller’s display name (for example, “Alice rolled 1d20+5 = 18”)

The feed automatically scrolls to show new entries as they arrive. If you scroll up to review older events, auto-scroll pauses. Scroll back to the bottom to resume auto-scrolling.

The GM can preview the scene at any past event. This is useful for checking what the map looked like before a series of actions, or for investigating what went wrong.

To preview a past state:

  1. Hover over any entry that has a version number — a clock icon appears on the right
  2. Click the clock icon to enter preview mode

While in preview:

  • An amber banner appears at the top of the log showing the previewed version (for example, “Previewing v42 of 68”)
  • The scene visually updates to show the state at that version
  • The command input bar is disabled
  • The previewed entry is highlighted with an amber ring
  • You can scrub through the timeline by clicking the clock icon on other entries without exiting preview

To exit preview:

  • Click Resume Live in the amber banner
  • Or type /rewind off (if the input bar is not disabled in your current view)

Resume Live restores the scene instantly from a captured snapshot — no server round-trip required.

From preview mode, you can permanently revert the scene to the previewed version.

  1. While in preview mode, click Revert to Here in the amber banner
  2. A confirmation step appears showing how many events will be discarded (for example, “Discard 26 events?”)
  3. Click Confirm to proceed, or Cancel to stay in preview

After reverting, all connected clients receive an updated snapshot and resync automatically. New events continue from the reverted version number.

You can also revert directly with /revert <version> (for example, /revert 42).

Role What you see
GM Everything, with rewind and revert on hover.
Player No Activity page. The Log tab is the game log, and its message box runs the slash commands a player may use.
Observer The same as a player.

Events only appear once the scene is active and connected, and the list starts when you open the table. If nothing has happened since, try rolling dice with /roll 1d20 to check it is working.

Check your connection. The feed relies on a live socket connection. Try refreshing the page — the feed repopulates from the event history on reconnect.

The log shows the most recent 500 entries since you opened the table. Older entries drop off the list, and a reload starts the list again. The full event history is preserved on the server.

Only the GM can use rewind. Players and observers do not see the clock icon on entries. Make sure you are clicking the clock icon that appears on hover, not the entry itself.

Revert is permanent and cannot be undone. The events after the revert point are deleted from the server. If you need to recover, contact your server administrator to check for backups.

When someone plays a card, the log doesn’t just name it — it shows it, full width, with what happened underneath. You can read the card that caused the number without going to look for it.

Hover a card in the log for two buttons in its corner:

  • Expand opens it large enough to read properly.
  • Flip opens it showing the back.

Once it’s open, F flips and Esc closes. There’s no play button on a card in the log — it has already been played.