Host for Players¶
Open it from Host for Players in the saga page's Saga Management chapter. It's the one place you host the saga and manage who joins. It stays open beside the game, so you can keep playing while it's open.
At the top, choose how players join:
- Remote seats (Their own Armarius, over the internet). Each player runs the app, which connects through a tunnel you set up yourself, such as Cloudflare Tunnel. See How to host for Remote seats.
- Browser or terminal (On your private network). The older way, over Tailscale or ZeroTier. See How to host for browsers and SSH. An address the internet can reach is refused unless you tick I know this is reachable from the internet.
Under it, the window says whether the saga is hosted, with Host or Stop Hosting. To switch the way players join, stop hosting first. Closing the app while the saga is hosted asks first, as it ends every player's connection.
For Remote seats it also shows the host's six words, which you read aloud on your group's call. It has three pages, chosen on the rail at the left: Requests, Seats and Log. The window looks for new requests every few seconds. The title, and Requests on the rail, count those waiting.
Players¶
Who may sign in is on the saga page's Saga Management, beside the Host for Players button. The Players list shows each player's role, the characters they play, and whether they can sign in from a Remote seat (✓ Ready, or why not).
A player's form has a Plays tick for each of the troupe's characters, and several players may tick the same one. A passcode needs at least 14 characters (see Changing or forgetting your passcode). Choose a player there and Issue Invite to invite them, and this window opens with the Invite.
Storyguides in troupe-style play. Give a player the role Storyguide to let them run the saga from their own seat. They see everything, such as Secrets, unknown records, Roll Tables and threats' stages to come. They can change any record, advance the season and change Saga Settings. What stays yours, on this computer only, is who may join and as what: the Players and their roles, this window, and deleting the saga.
Making someone a storyguide whose devices already have seats asks first, naming those devices. The change reaches their seat within seconds, and the Log notes it. Storyguides are marked "(storyguide)" in these lists, in the Log, and beside the trail when they're viewing a record.
To play a character yourself for a while, use Play as in the title bar. Hosting goes on, and its menu keeps Host for Players one click away until you choose Storyguide again.
When a storyguide advances the season from their seat, this computer backs the saga up first. Then it takes the saga in as it takes any save, keeping a player's change made meanwhile unless it touched the same thing. If two storyguides advance at once, the first wins. The second is told who advanced, and nothing of theirs is changed.
While the saga has players, your own window picks up what they save every few seconds. The page is drawn again, with a note at its foot such as "Anna changed Leandro; reloaded." It waits while you have a form or question open, so nothing you're typing is touched.
A player's change reaches only what's theirs to change: their characters, those characters' labs, familiars and season plans, and the covenants if you gave them covenant rights. It never removes anything hidden from them, such as a Secret. Where you and a player changed the same thing, the later save is kept.
A player needn't play a character to join. Once in, they can make their own with New Character (see Joining with no character yet). It arrives here named as theirs, with a note like any change, and the Log notes it too. Change or delete it as you would any character.
Host for Remote Seats¶
Host, with Remote seats chosen, asks:
- Tunnel address: the https address your tunnel gives you, such as
https://saga.example.com, with nothing after the name. - Tunnel: Cloudflare Tunnel, or another, such as ngrok or Tailscale Funnel. It tells the app where the tunnel says each player's own address is, so the limits on connections count each player apart.
- Port: the port on this computer the tunnel points at, 8790 unless another program has it.
The line under the fields says what to point the tunnel at (http://localhost:PORT) and the address the Invites will carry. The app listens on this computer alone, and only the tunnel reaches it. The choices are kept for the saga, outside the saga file.
Issue Invite¶
On Players, with the player chosen, or on Requests, Issue Invite asks which Player to invite. Players and storyguides are both offered, storyguides marked. Only those whose passcode has at least 14 characters, set since this rule began, are offered. The others are listed with the reason. A storyguide's device will see everything in the saga, and approving it says so.
The window then shows the line to send the player by chat or email, with a Copy button, and the host's six words to read them on the call. The line works once, on one device, for 24 hours. It's shown only this once and can't be shown again, so if you close it unsent, issue another.
Requests¶
When a player's app uses an Invite, their device waits here, with the player, the device's name, its three words and when it asked. Ask the player to read you the three words their screen shows. Approve asks whether they match before it gives the device a seat. Reject turns it away, and its Invite is spent. A request not decided within an hour lapses.
A player who has forgotten their passcode asks here too, from a device that already has a seat. Asks for says A new passcode. Check it's really them, on your call say. Then Set New Passcode opens their player form: type a new passcode and tell it to them. Setting one, here or on Players, answers the ask, and their device keeps its seat. Reject turns the ask down, and they keep the passcode they have.
Players can also change their own passcode from their seat. The Log notes it, never the passcode.
Seats¶
Each device given a seat, with the player, the device, its words, when it was last used, and when it expires if unused, or when it ended.
- Revoke ends the chosen seat. Its connection is cut within a second, and the device needs a new Invite to come back.
- Idle Expiry sets how many days a seat may go unused before it stops working, for this saga. It's 90 unless changed.
- Rotate Host Key gives the host a new key. Every Invite, waiting request and seat ends at once, and each player needs a new Invite and hears the new six words. If the saga is hosted, it starts again with the new key.
Log¶
What happened to Remote seats, newest first:
- Invites issued and redeemed
- requests approved or rejected
- sign-ins, wrong passcodes and lock-outs
- reads of the saga
- each record a player changed, and each change refused
- revoked and expired seats, and new host keys.
Show narrows it to one player. The log records who and when, never a passcode or a code, and keeps a year. It's kept outside the saga file, so players never receive it.
See also: How to host a saga, Players