What it does

Checking players in, recording results, correcting a result, dropping somebody, seating a late arrival and writing up a penalty all work offline and merge when you reconnect. Pairing a round needs authority, because two devices pairing the same round is the one thing that cannot be merged — so exactly one device holds it at a time, and the rule is published rather than left to chance.

5 rulesets ship for 4 games, each with its own tiebreaker chain. Nothing in the engine names a card or a deck, so a league that is not a card game runs on the same software.

Recurring series carry standings across every night. A season is a window over one series; a circuit spans whatever you say it does — every game, across rooms — with points by finish, a weight per series, and a best-of-N rule so somebody who works Fridays can still win it. The cut line is drawn on the public table, because “am I still in?” is the only question a player has.

A link from NetDeck or anywhere else, or the list pasted straight in — whichever they have. You see who has submitted and who has not, and you can start the round anyway, because a judge who cannot start while somebody is in the parking lot is a judge fighting the software.

A list is readable by the player who wrote it and by whoever runs the event, and by nobody else, ever — including after the night ends. There is deliberately no setting that makes them public.

Every state change in a competition is a command in an append-only log, so the audit trail is not a second thing that can disagree with the results — it is the record the engine replays. Recording a penalty never changes a result on its own: the console tells you what it carries and offers to do it, rather than moving the standings for a reason nobody watching can see.

Take registrations from your own website, seat a walk-in from the register, or have Discord post pairings the moment a round starts. Import a year of Fridays from a spreadsheet, and take everything back out whenever you like — schedule as CSV, the lot as JSON, no support ticket. The documentation is generated from the same code, so it cannot drift.

Every store, series and night has a calendar feed players subscribe to, so your schedule lives in their phone rather than needing a visit.

• Public — On your store page, in search, and in the calendar feeds players subscribe to.
• Only with the link — Not on your store page and not in search. Anybody you send the link to can see it and sign up — good for a private league night or a test run.
• Invite only — The link works and the page explains itself, but only you can seat people. Players cannot sign themselves up — for a qualifier or an invitational.
• Private — No public page at all — not even with the link. You run it from the console and seat everybody yourself. For a closed league, a staff night or a private booking.

And the insights page reads your own calendar back to you: who came back, who you turned away from a full room, which night draws best. A rate with too few players behind it is left blank, with the reason, rather than shown as a number that means nothing.

Point it at the event’s display page and it runs on its own — pairings, then standings, turning the screen over every twelve seconds and checking for changes the same way the player page does. Nobody clicks anything once it is pointed at the event.

Dark

Light