Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Pod Pass

A Pod is your playgroup inside ArcaneMetriX. It gives a regular table one shared place for its house rules, its game history, its play schedule, and its trade offers.

Pod features are PRO-gated. Access can come from your own individual PRO membership, or from a Pod Pass: a group subscription that gives four members of a pod PRO access through its seats. Members with their own individual PRO do not use a seat.

You can be in up to three pods at once, say your Thursday group, a shop league and an online table. Switch between them with the pod’s name at the top of the Pod tab.

Signed-out and non-PRO visitors see a preview of the Pod tab rather than any pod data.

When PRO Ends

Every pod feature needs PRO coverage, whichever way you have it: your own membership, a Pod Pass seat, or a promotional grant. If yours ends, the pod keeps your history: you stay a “previous member”, your games stay in the Game Log, and nothing is deleted. Until your PRO is back, though:

  • The Pod tab shows the preview instead of your pod, and Upkeep shows the pod as waiting for you (games you track meanwhile stay on the phone and sync once your PRO returns).
  • Your decks and collection stop being shared with the pod, whatever your sharing settings say.
  • If you own the pod, you cannot rename it, invite or remove anyone, or change its house rules.

Everything comes back as it was the moment your PRO does assuming you’re still in the grace period. You can still leave the pod, answer an invitation, manage your billing, download your data or delete your account at any time.

Creating or Joining a Pod

Any individual PRO member can create a pod from the Pod tab. The creator becomes the owner and controls the membership list, the house rules and the pod’s name (rename it from the pencil beside the name at the top of the Members dialog).

Owners invite people two ways:

  • By account: search for an ArcaneMetriX username and send an in-app invitation. The invitee accepts from their notifications.
  • By email: for someone who may not have an account yet. An email invitation works the same whoever the address belongs to, so it never tells the owner whether an address is registered, or to whom.

Pod names are checked like other text people see; a name that is refused says so beside the name field.

While an invitation is pending it holds one of the pod’s Pod Pass seats, so a pod cannot over-commit its seats by inviting more people than it has room for. When every seat is taken, you can still invite someone, but only a person with their own PRO can accept until a seat frees up.

Accepting an invitation while you are in other pods is fine; the app reminds you which ones. A fourth pod is the limit: leave one first.

Switching Pods

If you are in more than one pod, the pod’s name at the top of the Pod tab becomes a switcher. Pick a pod and every subtab (Hub, Game Log, Stats, Trade) shows that pod; the app remembers your choice on this device. House rules follow the pod you have chosen, so the Builder’s warnings and highlights are that pod’s.

Pod Pass Seats

A Pod Pass belongs to the person who bought it, not to a pod. It backs one of their pods at a time, and they choose which:

  • Buying for a pod you are in puts the pass behind that pod. Buying with no pod creates a new one called “My Pod”.
  • Seats add up. Each Pod Pass gives four seats, and a second member can put their own Pod Pass behind the same pod for four more, so two passes give eight. The app tells you when a pod already has a Pod Pass, and the rest of the pod is told when another one starts backing it.
  • Moving a pass. A holder can move their pass to another of their pods, or take it off. Members of the pod it left may lose their seats; they are told if so.
  • When a holder leaves, their pass goes with them and waits until they choose another pod; their subscription carries on. If the pod no longer has enough seats, the most recently joined members without their own PRO lose theirs first, and get them back, oldest first, when seats free up.

Everyone in a pod sees how many seats it has, for example 7 members and Pod Pass seats 5 / 8. The seat count only appears while a Pod Pass backs the pod. Whose PRO is their own and who holds a seat stays private: you see that about yourself only.

Added by Support. Now and then our support team adds someone to a pod past its seats. That seat sits on top of the pod’s Pod Pass seats and does not take anyone else’s. Everyone in the pod sees an Added by Support marker, and the seat count notes it (“+1 added by support”).

The Hub

The Hub subtab is the pod’s overview.

Members

Each member row shows their role, their status, when they joined, and their sharing preferences. Your own row also shows whether your PRO access is your own or a Pod Pass seat: how anyone else pays for PRO is theirs to know, so the pod is told only whether a Pod Pass backs it and how many seats it has. The owner also sees the subscription’s state.

Sharing is per-member, opt-in, and comes in two parts:

  • Collection sharing lets the rest of the pod see what you own in card lookups and the Trade subtab.
  • Deck sharing lets them open your private decks from Pod surfaces and log games with them. Your public decks are open to everyone either way.

Both are yours to change at any time, and they only ever apply inside this pod. A deck someone keeps private shows as A private deck wherever the pod would otherwise name it: in stats, in a session’s planned decks, and in the Game Log.

House Rules

House rules are how a pod records the things it has agreed on. They are a social guardrail, not an enforcement mechanism. Nothing is blocked, but the app will tell you when a deck disagrees with them.

Pod house rules showing a banned card, the allowed Commander bracket range, and mulligan settings

Five kinds of rule are supported:

  • Banned cards: a card your group does not play, even where the format allows it.
  • Allowed cards: a card your group does play, even where the format bans it.
  • Bracket requirement: the range of Commander brackets the pod plays at, shown against the full 1–5 scale.
  • Mulligan rule: how mulligans work at your table (see below).
  • Custom: anything else, written in your own words.

Card rules can apply to all formats or to one specific format.

Once a card rule exists, that card is highlighted in a warning color wherever you build (in the Builder’s grid, list, and stack views, and in Search) and the card’s detail modal explains the ruling underneath its Format Legality badges. The badges themselves keep reporting the format’s real legality; the pod’s ruling is shown alongside it, never instead of it.

Mulligan Rules

The mulligan builder records the mechanics of a mulligan: how many cards you draw, scry, and bottom to start, how each of those changes per mulligan taken, and how many mulligans are free. Presets for the Original, Paris, Vancouver, and London mulligans fill the fields for you, and you can edit from there.

You can set one mulligan rule per format, so a pod that plays London for Commander and something else for its cube night can record both. A rule with no format set is the pod’s default.

Your pod’s mulligan rule drives the Opening Hand Simulator automatically: open a deck’s Test subtab and the simulator uses the rule matching that deck’s format, showing which rule it applied. You can override it for a session if you want to compare.

Note: Scry is recorded on a rule but is not yet simulated. When a rule uses scry, the simulator says so rather than quietly reporting a number that ignores it.

Scheduled Sessions

Schedule a play session with a date, time, time zone, format, and either a physical venue or an online platform. Members RSVP as Going, Maybe, or Can’t make it, and anyone going can share the decks they expect to bring.

Every session offers one-click calendar export to Google Calendar, Apple Calendar, Outlook on the web, or a downloadable .ics file. No calendar account access is required.

Sessions stay visible for seven days after they happen, with a shortcut to log the games that were played.

Game Log

The Game Log records what actually happened at the table. A minimal entry is just the players and their finishing order; everything else is optional and can be filled in when it matters.

Tip: The easiest log entry is the one you never type. Upkeep, the free life counter for phones, logs every game a signed-in member tracks at the table, with placements, decks, eliminations, turn count and a turn-by-turn life chart, and the pod’s ratings update as the game ends. Such entries show a Tracked with Upkeep badge and a recap.

A detailed Pod Game Log entry with placements, decks, life totals, eliminations, and commander damage

Per game you can record the format, starting life, turn count, notes, and for Commander, a bracket target, the power level the table agreed to play at. Setting a bracket target sorts each player’s decks so matching ones are suggested first, without preventing anyone from bringing something else.

Per player you can record:

  • Finishing placement, set by dragging players into order
  • Deck played, including decks borrowed from another member
  • Ending life total and poison counters
  • Commander and partner cast counts
  • The turn they were eliminated, and who eliminated them (including themselves)
  • Commander damage taken, per opposing commander

Guests and Unpublished Decks

Not everyone at a table has to have an account, and not every deck has to be saved in ArcaneMetriX. The Game Log handles both:

  • Guest players can be tracked by name and later linked to a real member if they join, which moves their whole game history onto the member’s record.
  • Tracked decks let you log a deck that only exists in paper, and later link it to a published deck without losing the games already recorded against it.

Stats

The Stats subtab turns the game log into a picture of how your pod plays.

Pod statistics showing member win rates and head-to-head records

  • Member win rates and a head-to-head matrix, including how often each player has personally knocked each other player out.
  • Deck win rates, with filters by name, format, and player.
  • Pod totals: games logged, average game length, eliminations, commander damage.
  • Who does what: share of eliminations, average survival turn, commander damage dealt, poison handed out, and life lost.
  • Finishing positions: each player’s spread of 1st through 5th-plus.
  • Favourite decks: each player’s most-sleeved list.
  • Pace: average turn count per format, broken down by bracket target for Commander.
  • Superlatives: a title for each player, one each, based on what they do at the table.

Trade

The Trade subtab is where the pod’s cards move.

The Pod Trade view showing each member’s recent wishlist cards

  • Pod wishlists: what everyone is looking for, browsable with the same List, Grid, Stack, sort, and filter tools as Builder and Collection.
  • Collections and trade binders: every shared printing, with a “tradable only” filter. Private details such as notes, acquisition costs, and storage locations are never shared.
  • Recent wants: each member’s five most recent wishlist additions.
  • Ready to match: potential player-to-player trades, ordered by approximate value, with a note on how close each side is.

Only members who have turned on collection sharing appear in the collection browser. Value estimates are a starting point for a conversation, not an appraisal; you should confirm condition and price together before trading.

Leaving and Removing Members

Leaving a pod, or being removed from one, splits your data in two:

  • Your logged games stay with the pod. A shared game log is the group’s history, and removing past results would corrupt every win rate and head-to-head record built on them.
  • Your personal data leaves with you. Your decks can no longer be opened from any Pod surface, and your collection disappears from the Trade subtab.

Former members remain listed as inactive so historical stats still resolve to a name. A pod owner can additionally choose to erase a former member’s play data entirely, which removes their games from the pod’s history and drops them from the member list.

Anyone can leave a pod at any time, the owner included; your other pods are not affected. When the owner leaves, the pod passes to a member whose Pod Pass backs it, or else to the longest-standing member with their own PRO. If nobody can take it on, the pod is disbanded. If you hold a Pod Pass behind the pod, it leaves with you, and the app tells you how many members will lose their seats before you confirm.

Disbanding a Pod

The owner can disband the pod from the Members dialog. Everyone’s membership ends, so they are free to join or start other pods straight away, and any Pod Pass behind the pod goes back to its holder to put behind another pod; nobody’s subscription is cancelled. Everyone in the pod is told.

A disbanded pod is kept for 90 days. Within that time our support team can restore it, bringing its members back, except anyone who is by then in three other pods (they are told). After 90 days the pod is anonymized, as described in the Privacy Policy.