Tournaments (beta)

Tournaments for any game, in two flavours:
- Counter-Strike 2 — the automatic one. The portal builds a server per match and retires it after; the game reports its own results and the bracket moves by itself.
- Games with real head-to-head play — Minecraft (both editions), V Rising, Palworld, Terraria — pick them from the list; and any other contest goes through the "Other game…" field, because a building contest decided by the organizer is a tournament too. Matches are played wherever you play (a standing server, another machine, a couch), and the result comes from the people in it: each captain reports the winner, and agreement decides the match. If the two reports disagree, nothing moves and the organizer settles it through Decide…. Bracket, seeding, scheduling, standings and the public page work identically.
Three formats
Picked when the tournament is created, because the bracket's shape is the tournament's shape:
- Single elimination — lose once, go home. The classic; shortest night.
- Double elimination — lose once and you drop into the losers bracket; lose twice and you are out. The winners-bracket champion meets the losers-bracket survivor in a single grand final (no bracket reset — one series decides it). Needs at least three teams.
- Round robin — everyone plays everyone once; the standings crown the champion (wins, then map difference, then round difference). Best for small groups that want many matches rather than sudden death.
Byes work in every format: an uneven field gives the top seeds a free pass, visibly, and in double elimination a bye never produces a losers-bracket opponent — the bracket accounts for that on its own.
The feature wears a beta label until it has been tested and validated end to end — expect rough edges, and say what you hit.
Teams first
Everyone can create a team on a tournament's Teams tab; whoever creates it is its captain and manages the roster. One thing matters more than it looks: Steam64 IDs. The match server reserves player slots by Steam ID, so a member without one cannot claim their seat. Fill them in on the Teams tab — each member can set their own, the captain can fix anyone's. (Find yours on your Steam profile URL, or via steamid.io — it is the 17-digit number.)
The tournament's life
- Draft — an operator or the owner creates it: players per team, best of 1/3/5, the map pool, a team limit. A pool larger than the series length means the teams veto in-game, exactly as they know it from FACEIT; a pool of the same size plays in order.
- Registration — captains enter their teams. The organizer can nudge the seeding (the arrows next to each entry); random is fair, but two top teams meeting in round one is worth preventing. While a match server lives, it also stands on the Servers page like any other card, wearing a match badge: open it for player counts, performance charts, live logs, the console and Files. What it refuses is a steering wheel — no restart, stop or settings — because its lifecycle belongs to the tournament, and the card retires itself with the match.
- Running — starting builds the bracket. Uneven fields get byes: the top seeds skip round one, visibly. The organizer schedules each round (in double elimination the winners rounds, losers rounds and grand final are each their own column); fifteen minutes before a match's time the portal builds its server — fresh password, its own port, its own Steam token — and pings Discord when it is ready. Players hit How to join on their match for the console connect line. MatchZy runs the competitive flow in-game (ready-up, knife round, veto) and reports every score back; the bracket moves the moment a series ends, and the server is retired along with its token.
- Finished — a decided final (or, in round robin, the last match) crowns the champion and closes the tournament. The page stays, as the archive.
Check-in
Each match card carries a Check in button for the two captains: one click says "we are here", and a green ✓ appears next to the team for everyone — the organizer, the other team, the public page's spectators. Check-in never blocks a match (a LAN party does not want a bracket that refuses to proceed over a forgotten click); it is the readiness signal, and the paper trail when a no-show becomes a forfeit.
Reporting results (non-CS2 games)
For every game that cannot report its own scores, the match card shows the two captains a "<team> won" pair of buttons once both teams are known. One captain reports; the result stands the moment the other captain reports the same winner. Disagree, and the card says so — reports disagree — and the match waits for the organizer's Decide…, which is exactly the escalation a disputed scoreline deserves. CS2 matches refuse self-reports; the game already told the truth.
Cloning
Next week's tournament is usually this week's with a new date. Clone (on the tournament page, organizers only) copies the settings — game, format, team size, series length, map pool — and the entered teams into a fresh draft with its own public address. Matches, results and seeds stay behind; a new event earns its own.
The public page

Every tournament past its draft has a shareable, read-only page at /t/<its-name> — the public page link on the tournament. Live bracket, scores as they happen, the champion afterwards. Team names always, player names only when the organizer flips the per-tournament switch — and never passwords, connect info or anything else that belongs inside.
Publishing through Cloudflare Access? Access guards /t/... too. To make the public pages genuinely public, add an Access application for the path your-portal/t/* with a Bypass policy; everything else stays behind the door.
When reality disagrees
The organizer's word outranks the game. The Decide… button on any match names a winner — with a mandatory reason that lands in the activity log — and is also how a no-show becomes a forfeit. A result can be corrected until the next round's match starts; after that, correct that match instead. Automatic byes downstream of a correction heal themselves: a bye that went to the wrong team because of the original result is re-derived, while anything actually played or decided by an organizer stays untouched.
What it costs the machine
A CS2 server wants ~2 GB RAM and a core or two; the shared installation is ~35 GB on disk, downloaded once on the first match ever (expect that first provision to take a long while — do it before tournament night, not during). Two matches run at once by default; the game ports (27051-27058) follow the same forwarding story as every other server — see Networking and ports.
GameKeepr