Both player loss in elimination tournament

[ckocank]

Due to #160
I know there can't be 2 player lose at the same time but I want to make this case works, any idea how?

Both player will be eliminated at the same time.

[Drarig29]

Can you give more context? What game is it? How can both of them lose?

[ckocank]

Can you give more context? What game is it? How can both of them lose?

I have a condition that both player must have met before the match start.
If one player fail to match the condition, the other will win.
So both player fail to match the condition, they will be eliminated.
In round-robin, I can set a match draw but not elimination.

[Drarig29]

Can you forfeit them instead?

[ckocank]

Can you forfeit them instead?

https://drarig29.github.io/brackets-docs/reference/manager/functions/helpers.setForfeits.html
Is this the fuction you are talking about?

[Drarig29]

https://drarig29.github.io/brackets-docs/reference/manager/functions/helpers.setForfeits.html Is this the fuction you are talking about?

No, generally you should not have to use helpers. I'm talking about using the usual manager.update.match() method.

You can pass forfeits there:

await manager.update.match({
    id: YOUR_MATCH_ID,
    opponent1: { forfeit: true },
    opponent2: { forfeit: true },
});

See unit tests:

brackets-manager.js/test/round-robin.spec.js

Lines 212 to 225 in 8c2efdc

	it('should set two forfeits for the match', async () => {
	await manager.update.match({
	id: 0,
	opponent1: { forfeit: true },
	opponent2: { forfeit: true },
	});
	const after = await storage.select('match', 0);
	assert.strictEqual(after.status, Status.Completed);
	assert.strictEqual(after.opponent1.forfeit, true);
	assert.strictEqual(after.opponent2.forfeit, true);
	assert.strictEqual(after.opponent1.result, undefined);
	assert.strictEqual(after.opponent2.result, undefined);
	});

[Drarig29]

I have a condition that both player must have met before the match start.

I'm going to close the issue because this is the only solution, and you can say that "players failing to match those conditions will be forfeited". Cheers! 🥂

[ckocank]

Thanks for your replied.
I tried

await manager.update.match({
          id: match.id,
          opponent1: { id: match.opponent1.id, forfeit: true },
          opponent2: { id: match.opponent2.id, forfeit: true },
        });

But it return
Error: There are two forfeits.
I can only forfeit 1 player.

[Drarig29]

Ha... OK I think I designed it this way (double forfeits are only supported in round-robin), but I agree there is a use case.

I'll try to fix this so you are able to have 2 forfeits.

[enchantinggg4]

Hello, any updates on that? Having same use case, if no player shows up to an elimination match, i need to forfeit both
and it should also work for bo-3/5/7 and etc...
It's tricky though: for bo-1 there can't be a situation with mixed forfeits and played games. For example:
bo3:
1st game = 1:0
2nd game = 1:1
3rd game = double forfeit, results in a draw, which is impossible for elimination matches. it seems wrong to treat this draw same way as
bo1:
1st game = double forfeit + auto forfeit parent match.

[Drarig29]

"3rd game = double forfeit, results in a draw, which is impossible for elimination matches". It seems wrong to treat this draw same way as "BO1: 1st game = double forfeit + auto forfeit parent match"

My approach would be:

• No draws allowed in elimination stages, but double forfeits are allowed: they disqualify both opponents.
• If match "A vs. B" has a double forfeit, then it creates a BYE in next matches in winner bracket and loser bracket.
• Double forfeits in games of a BO-X match will also disqualify both opponents because it's a failure to compete, and auto forfeit the parent match. (Even if it was a BO3 with some played games)

TLDR:

• Double forfeit ≠ Draw. It's a disqualification (administrative), not a competitive outcome.
• The logic:
  • Single forfeit = competitive concession (opponent wins)
  • Double forfeit = failure to compete (both DQ'd, not a draw)

@enchantinggg4 would that work for you? (cc. @ckocank)

[enchantinggg4]

Overall - i like idea with a double BYE
Not sure about if it should be a double forfeit in cases when games were played in BO-x.
I mean, there could be different cases and different tournament rules. Imagine we have a best of 3 match, here are some cases to consider:

Case 1: Both opponents are late to first game, hence they both "lose". In my point of view, this should make a match essential bo1 instead of bo3.

Case 2: BO3, score is 1-0, same as Case 1 - match is resolved, because there a game is "spent" and what matters - losing team lost its chance to make a comeback to score 1-2

Case 3, the hard one: score is 1-1, both teams didn't come. Here we can do a double forfeit and it makes sense - they both played, but somehow late to final game.

What also to consider: tournament might have different rules. Fast tournaments are ok with disqualifying an opponent as soon as they don't come to any game, some are not. So I suggest introducing 2 signatures, something like that:

1. updateMatchDoubleForfeit(matchid) - sets double forfeit, results in BYE in next matches
2. cancelGame(gameid) - marks game as cancelled, and if match was bo3, it now requires only 1 win to complete
   "Cancelled" match status is also useful, because it fills missing status for games in bo3/5 matches which were not played:
   if BO-3 ended with a 2-0, 3rd game not needed, but there is no appropriate status for it. I use archived, but it seems not intuitive

[enchantinggg4]

And of course, cancelGame(gameid) for BO1 should do the same as double forfeit