Skip to content

Join a Saga

Join a saga your storyguide hosts on their own computer, from your own copy of Armarius, over the internet. Click Join a Saga on the title page or the Sagas shelf. The first time takes a few steps. After that you sign in with your passcode.

The first time

  1. Paste the invite your storyguide sent you, a line that begins ARM1. It works once, on one computer, for a day.
  2. Check the six words. Your storyguide reads six words out on your call. Compare every one with the six on your screen, since the first two or three alone are far easier to fake. If all six match, click They match.
  3. Stop if they differ. If they don't match, click They don't match. The invite may have been changed on its way to you, so nothing is sent. Ask for a new one, by another way if you can.
  4. Name this computer, its own name to start with, so your storyguide knows which device is asking. Then click Ask for a Seat.
  5. Read your three words to your storyguide. When they match what their screen shows, they let you in, and the window moves on by itself.
  6. Type your passcode, the one your storyguide gave you (at least 14 characters). The saga opens.

The saga then stays on your shelf, marked Hosted elsewhere.

When your version and the host's differ

Joining compares your Armarius with your storyguide's, from the host's greeting (nothing is asked of GitHub).

  • Another major version (the first number differs) stops you joining. If yours is the older, it says the host runs Armarius X and you run Y, so update to the host's major version, and Update opens the app's Releases page. If the host's is the older, it says "Your storyguide's Armarius is older (X). Ask them to update.", with no button.
  • Another minor version (only the second or third number differs) lets you play. In the joined saga, the settings gear wears its "!" seal and the Settings window's Update row says "Your host runs Armarius A, and you run B. You can play, but these versions haven't been tested together, so some things may behave oddly." It offers Update when yours is the older.

On the storyguide's side, the Players list in Saga Management notes a player who last joined on another version, as "4.13.1, not tested with yours". Nothing is ever blocked by it.

Coming back, and leaving

When the saga you played last is a joined one, Open Saga on the title page opens it, as it does a saga of your own. Otherwise click the saga on the shelf and type your passcode. You stay signed in until you close the app, leave the saga, or your seat ends. Going back to the Sagas shelf and opening it again doesn't ask for the passcode.

If the connection drops while you play, the app connects again by itself. Changes you made meanwhile are sent once it's back, and closing the app before then asks first.

If your seat has ended, the app says so, and you'll need to ask for a new invite. A seat ends when your storyguide revokes it, when you don't use it for a long while, or when they give their host a new key. Leave Saga on the saga's card forgets this computer's seat. To come back you'll need a new invite.

Changing or forgetting your passcode

Change Passcode on the saga's card changes it. Type the passcode you have now, then the new one twice. It needs at least 14 characters, and a few words you'll remember, such as "grey owl over the mill", are easiest. A wrong current passcode counts toward the lock-out, as signing in does. You stay signed in, and from then on you use the new one on every computer you join from.

Forgotten it? Click the saga on the shelf, then I've forgotten my passcode under the passcode. Your storyguide is asked. They check it's really you, on your call say, and give you a new passcode, which you type there. This computer keeps its seat, so you need no new invite. Only a computer that already has a seat can ask.

While you play, your pages show what you may see, and you change only what's yours:

  • your characters, their laboratories, familiars and season plans
  • the season plans of characters you're Steward of
  • your teaching asks and answers
  • the covenants, if your storyguide gave you covenant rights.

Joining with no character yet

You can join before you have a character. Your Characters on The Troupe then says "None yet", with a New Character card. Click it to make your own, a magus or a companion. You can make a grog too if your storyguide gave you covenant rights, since a grog joins the covenant's household. It's yours from the start, named as played by you, and opens on its Creation Worksheet so you can carry on building it. Your storyguide sees it at once and can change or delete it like any other. You can't make one for someone else or for the whole troupe, since who plays a character is the storyguide's to say.

Every few seconds your pages pick up what others saved, with a note at the window's foot. When your storyguide advances the season, your window turns the season's dial too. If someone else has the record you're on open, their name shows beside the trail, such as "◉ Bruno is also viewing", so you can agree who changes what. A storyguide is marked as "Bruno (storyguide)".

If the host made you a storyguide, you see the whole saga and may do all a storyguide in troupe-style play may, Advance Season included. If another storyguide advanced first, your window shows the saga as it now is, so look before advancing again. Who may join, and as what, stays the host's, and Saga Management says so. When the host changes your role, your window follows within seconds and says so.

What a host can and can't see or do

  • Your saga, as you may see it, is all you receive. Secrets you haven't been told, places and people you don't know of, and other things your storyguide keeps to themselves never leave their computer.
  • Nothing is stored on your computer but this device's seat, kept in your computer's own keychain: Windows Credential Manager, macOS Keychain or a Linux Secret Service. The saga stays in memory while it's open and is gone when you close it.
  • Your passcode never crosses the internet. Signing in, your app proves it knows it in a way that's useless to anyone who overhears, and to anyone pretending to be the host. When you change it, only the new one's scrambled form is sent, inside the encrypted connection. That's the form the host keeps, from which the passcode can't be read back.
  • The six words are your check that you reached your storyguide, not someone in the middle. Compare all six on your call each time you join from a new invite.
  • What your storyguide's computer sees: your internet address, as any website does, when you play, and the changes you make. Each change is recorded in their log by which record it touched, never what you typed. Their tunnel company sees that you connected, not what passed.
  • What it can't do: reach anything on your computer. The app takes only saga records from it and runs nothing it sends. Every record is checked against the form the app's records have before it's used. Anything else is refused, and the app names the field it couldn't read.

What keeps you safe

In plain words, what happens when you join and play:

  • The handshake. Before anything else, your app and your storyguide's set up a private, encrypted connection of their own, inside the one the tunnel carries. Nobody on the way, such as your network, the internet or the tunnel company, can read it or change a word of it unnoticed. A changed message ends the connection. Each connection has fresh keys, so a recording of an old one is no use later.
  • The pin. Your Invite carries a fingerprint of your storyguide's computer, its pin. Your app checks the host it reaches against that pin before it sends anything at all, and stops if they differ. The six words are the same pin, made easy to read aloud. Matching them on the call proves nobody swapped the Invite on its way to you.
  • Your device's seat. Once your storyguide approves your device, it gets a key of its own, kept in your computer's keychain. It works only with your passcode, only for this saga, and your storyguide can end it at any time. Leave Saga ends it from your side.
  • The limits. A wrong passcode slows your device down, so nobody can guess it quickly. Three tries are free, then the waits grow, and nobody else's device can lock you out. Your storyguide's computer closes a connection that floods it or sends what it doesn't understand, and turns away too many connections at once.
  • If something looks wrong, such as six words that don't match, a passcode you know being refused, or a seat ended that you didn't leave, stop. Ask your storyguide on your call before trying again.

See also: How to host a saga