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 whose owner supplies PRO access to members through four subsidized seats. Members with their own individual PRO do not consume a seat.

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

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 subscription, the membership list, and the house rules.

Owners invite people two ways:

  • By account: search for an ArcaneMetriX username or email and send an in-app invitation. The invitee accepts from their notifications.
  • By email: for someone who has not created an account yet.

While an invitation to a non-PRO person is pending it reserves one of the pod’s subsidized seats, so a pod cannot over-commit its four seats by inviting five people at once.

You can only belong to one pod at a time (for now).

The Hub

The Hub subtab is the pod’s overview.

Members

Each member row shows their role, whether their PRO access is individual or supplied by the Pod Pass, their status, when they joined, and their collection-sharing preference.

Collection sharing is per-member and opt-in. Turning it on lets the rest of the pod see what you own in card lookups and the Trade subtab, and lets them open your decks from Pod surfaces. It is yours to change at any time, and it only ever applies inside this pod.

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.

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.

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.

  • 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.

  • 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.

If you are the owner of a pod backed by a Pod Pass, you cannot leave without transferring it; the oldest eligible individual-PRO member becomes owner.