From an invite code to the next turn.

1. Give your game a home.

The GM creates a campaign, selects a game, and adds a name and optional description. The game determines the character choices and attributes available to the party. You can return to the campaign between sessions, rather than assembling a new roster for every fight.

2. Bring in the party.

Share the campaign's invite code with players who want their own view. After signing in, they use the code to join and choose a character. If someone would rather stay on paper, the GM can add them as a guest by name. Both kinds of player can have a seat at the same table.

3. Get ready around the table.

Arrange the seat cards in the order people are sitting and mark who is present. When it is time for initiative, work through the table and enter each player's result. This gives the GM a consistent way to collect rolls without jumping between names.

4. Run the encounter together.

Start the fight, add opponents as needed, and advance through the turn order. The GM updates combatants' hit points and conditions. Players with the campaign open can follow the current turn and see when they are next; character resource changes are shared with the table.

5. Keep the campaign ready for next time.

Ending an encounter does not mean rebuilding the party. Campaign membership and character records remain, and guest hit points persist between fights. Review those values when the party rests or the next session begins; your group decides when healing or resource recovery applies.

You can use a single GM screen or let players connect in their browsers. Connected views need an internet connection to receive live updates.

A session in practice: the missing ferry.

Imagine the party arrives at a riverside village and discovers that the evening ferry has vanished. The GM already has a campaign called The North Road, with three members and one guest. Everyone can begin talking to villagers immediately; there is no encounter to configure until the fiction actually calls for one.

When the party reaches the landing, two figures emerge from a stranded boat. The conversation becomes a fight. The GM checks attendance, asks for initiative around the table, and enters each result. The guest is included just like the other participants, even though that player is using a paper sheet.

During the encounter, a player checks how many hit points their character has left while another considers a rescue attempt. The GM advances turns and records changes. The tracker provides the shared order; the players decide what to attempt and the GM describes what happens.

Decide what your group will keep where.

Before the first session, choose where the authoritative record of each resource will live. If someone uses both a paper sheet and GM Console, agree when they will copy changes across. Two different hit point totals are usually a coordination problem, not an interesting mystery.

Keep long adventure notes in your notebook or preferred writing tool. Use the campaign description for a short premise, and the app for the roster and supported session values. That division gives everyone a clear answer to “Where do I look?” without requiring you to move a whole campaign archive.

Keep three simple habits.

• Check before play. Confirm the active campaign, selected characters, attendance, and current resources. This is particularly useful if the group alternates between adventures.
• Say changes aloud. Announce damage, healing, and conditions before recording them. The player can catch a mistaken name or amount while the moment is still fresh.
• Close deliberately. End the encounter, check any recovery the group has resolved, and tell everyone where the next scene will begin.

These habits also make returning after a break easier. The software can hold a value, but a short spoken recap explains what that value means in the story.