Skip to content

The activity feed

The activity log is the gameplay event feed in your VTT scene. It shows a running timeline of everything happening in the session — combat turns, token movements, dice rolls, resolutions, and more — so you always know what just happened, even if you looked away for a moment.

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

The activity log lives in the scene sidebar. Click the ScrollText icon in the sidebar tab bar (the rightmost tab, next to the Initiative panel) to open it.

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” or “Combat started”)
  • 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
Indigo Combat Combat started/ended, combatant joined/removed, round changes, turn advances
Grey Token Token added/removed, moved, updated, resized
Amber Fog Fog revealed, reset, visibility changed, strokes painted/erased (GM only)
Green Dice Local and remote dice rolls from all players
Orange Targeting Targeting started, updated, confirmed, cancelled
Purple Resolution Resolution enqueued, response requested/submitted, resolved, cancelled
Grey System/Command Slash command errors and feedback

Map-editing events that are not gameplay-relevant are filtered out: wall changes, grid changes, shape changes, light changes, effect changes, token group changes, and token vision changes. These events still happen on the server and are applied to your scene, but they do not clutter the activity feed.

Some events are only visible to the GM, including fog of war changes (painting, erasing, revealing, fogging). Players and observers will not see these entries in their feed.

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 All events, including fog changes. Rewind and revert controls on hover.
Player All gameplay events except fog changes. No rewind/revert controls.
Observer Same visibility as players. No rewind/revert controls.

Events only appear once the scene is active and connected. If the scene has had no activity, try rolling dice with /roll 1d20 to verify 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 feed shows the most recent 200 events. Older events are discarded from the client-side buffer. 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.