Skip to content

feat(tournaments): map veto on or off, a wingman preset, and a veto countdown bar - #755

Merged
sivert-io merged 1 commit into
mainfrom
feat/veto-off-wingman-preset
Oct 12, 2026
Merged

sivert-io merged 1 commit into
mainfrom
feat/veto-off-wingman-preset

Conversation

@sivert-io

Copy link
Copy Markdown
Collaborator

From tonight's test.

  • Veto switch — settings.cs2.veto (default on). Off: usesPreMatchPhase false (new optional integration hook, used by Scheduler.startTournament and the bracket's initial statuses), isReadyToAllocate true, the veto timer skips the tournament, and matchConfig draws the maps from the pool (drawMaps, seeded by the slug). Map rule: one map or more.
  • Wingman preset — button on the maps step: wingman-fitting maps, mapMode: 'wingman', veto off, MR16. Wingman matches use players_per_team: 2.
  • Veto countdown bar — TurnBar at the top of the veto for both teams and spectators, every step incl. side pick (turnDeadline/turnSeconds were already sent to everyone).
  • Locales en + nb. Test: tests/api/cs2-no-veto.spec.ts.

🤖 Generated with Claude Code

…ountdown bar

From the 2026-10-12 test:
- A BO1/BO3/BO5 tournament always ran a veto and wanted exactly 7 maps.
  The veto is now a switch (settings.cs2.veto, default on). Off: no veto
  phase anywhere (start, later rounds, the turn timer), each match plays
  maps drawn from the pool (the same draw on every config read), and one
  map or more is enough.
- "Set up as wingman" on the maps step: CS2's wingman maps, wingman map
  type, no veto, 16 rounds. A wingman match is 2v2 whatever the team size
  says (bot fill fills to two a side).
- The veto shows the turn's time to everyone, every step including the side
  pick: a bar that drains, with the seconds left.

Core gets one optional integration hook, usesPreMatchPhase(tournament).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sivert-io
sivert-io merged commit 5cdc242 into main Oct 12, 2026
24 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 12, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant