[Protocol] Share tournament messages and report draws explicitly

- TournamentPlayer/TournamentPairing/TournamentSettings move into
  serverinfo_tournament.proto, imported by both the tournament event and
  the tournament game commands, so Command_CreateGame reaches them without
  crossing the command/event boundary
- Command_CreateGame carries the full TournamentSettings instead of a
  duplicate games_per_match field, keeping game creation and mid-game
  changes on one wire representation
- draw results are explicit: Command_ReportMatchResult and
  TournamentPairing gain is_draw, so a report stays distinguishable from
  an unset -1 winner
- pairing match-wins are uint32 like the other game counts
This commit is contained in:
Lukas Brübach 2026-09-02 08:43:25 +02:00 committed by GitHub
parent e82b311c8b
commit dca6fdf17f
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 45 additions and 27 deletions

View file

@ -1,4 +1,5 @@
syntax = "proto2";
import "serverinfo_tournament.proto";
message RoomCommand {
enum RoomCommandType {
LEAVE_ROOM = 1000;
@ -70,8 +71,8 @@ message Command_CreateGame {
// share decklists with all players when selected
optional bool share_decklists_on_load = 14;
// number of games per match in tournament mode (e.g. 3 for best of 3)
optional uint32 games_per_match = 15 [default = 1];
// tournament settings shared by game creation and mid-game changes
optional TournamentSettings tournament_settings = 15;
// whether this is a tournament game
optional bool is_tournament = 16;