Tournament Round Ended Unexpectedly

[nik592]

If by maxTime you mean the time on each players clock, then it needs to be adjusted by a factor of 1/2, not 2, because 1/2 of the day the clock isn't running.

No, I mean, the max time per table is set by the tournament creator - 5 days, 15 days, etc. I think all are in days. And since playing hours only use 12 hours per day, then max time per table should be doubled in these tournament.

As a tournament host, when I set a round time at 7 days, I DO NOT want it dragging on for two weeks. I choose that time frame because the game can be completed in that time frame, even if players only play during playing hours. This is how it worked before and how we expected it to continue to work.

It's up to the host to be sure 7 calendar days is enough time.

Hang on, so I might be misunderstanding how it works then. I thought player time was correct, it was just that the games were ending before player time was used up. So the bug is that players should only be given half the time in this case? As in 3 player game with a 3 day timer, each player only gets 12 hours of play time, rather than 1 full day each?

As I say, I don't play tournaments with playing hours, so I've never really looked into how they work. Being that the bug is being typically described as the rounds ending early, that's how I was interpreting the bug. But really the bug seems to be that players are being allocated twice as much time as they should be - so you're quite correct, that the fix is to adjust player's max time by a factor of 1/2.

But as we agree, this isn't a complicated fix, and should have been done weeks ago.

[Meeplelowda]

So the bug is that players should only be given half the time in this case? As in 3 player game with a 3 day timer, each player only gets 12 hours of play time, rather than 1 full day each?

This is correct. Of course, like non-tournament games, you aren't prohibited from playing outside the playing hours. And if no playing hours were set your clock could possibly be running down while you sleep, so that would be dead time anyway. That said, 3 days would be far too short for any game I play. My shortest setting is 5 days for 2p games. It would be longer if I ever venture to do a 3+ player game.

Being that the bug is being typically described as the rounds ending early, that's how I was interpreting the bug. But really the bug seems to be that players are being allocated twice as much time as they should be - so you're quite correct, that the fix is to adjust player's max time by a factor of 1/2.

Yeah, it appears to be ending early because with properly set player clocks it's impossible for the round to end based on time while everyone still has time on their clock. So to the players it looks like the round is ending "early" because no one is in the negative on time, whereas it's actually ending when the tournament settings said it was going end, e.g., after 3 calendar days.

Here is a warning I posted:

The time on the clock is not correct. We are starting with twice as much time on the clock as we should have. Remember, each round is only TEN DAYS. The game will end after TEN DAYS regardless of how much time is on your clock. This affects everyone, but particularly Group 2 where only one table has finished after 5 days while all of Group 1 finished. Vote for this bug report to get this fixed: /bug?id=209956

[dschingis27]

A related problem comes in when you consider that BGA queues your games in progress by personal time left. Some power users (with more than 60 turn-based games running at once) rely on that mechanism, they prioritze the games where they have less time left on their clocks. Fair enough. But that means some players don't even notice (or too late) that they are due in the games with playing hours set.

BGA really made it an art (that they mastered) to ship an unfinished product. I really don't get it how they leave this bug and the problem with player ids breaking ties in multi-eliminations out in the open.

These problems aren't things that live in a small niche, rather they affect a broad user base. They are no pesky feature requests that only power users or top Elo players keep ranting about, they are literally problems that break the tournament experience particularly for newer users.

[Timoteo32]

Thanks for the insight. I wasn't asking for troubleshooting, I didn't think it was a bug, I just wasn't sure how tournaments worked, if/who messed up, and how to plan for it.

I also don't understand why it uses time left to decide who wins instead of score. In the case where no one ran out, this doesn't make any sense.

[Meeplelowda]

I also don't understand why it uses time left to decide who wins instead of score.

Some games don't even have a score, and in many games, even if someone has a higher score they may be in an objectively losing position. For example, they may have no way to score any more points and their opponent can pass them. You mentioned in another thread that you play Wingspan, so I'm sure you've seen exactly that scenario at some point.