New Tournament Pages are here: Better, Faster, and Mobile-Friendly!

[Meeplelowda]

How do we identify the developer that can fix https://boardgamearena.com/bug?id=209956 (currently 44 upvotes)?

Unlike games, for which the developers are publicly known, sitewide features like this don't necessarily have a known developer. For all we know the person responsible is some BGA software engineer who may not even have a BGA account, and if they do, they only use their account for testing and don't read the forums.

I suspect this is a very easy fix (make sure 12hr playing times are reflected in initial game timer).

Given that it used to work before the tournaments makeover, it is reasonable to think the fix is easy: just roll it back to what it was before. But whoever made this change may not have understood how playing hours function in tournaments and may have rewritten the tournament timing functionality in a way that it isn't straightforward to reintroduce this into the current code base. I.e., they can't just copy/paste the old code.

[Meeplelowda]

After a flurry of fixing things that were working just fine and got broken by the tournament pages overhaul, has BGA quiet quit this task? There are still things that are broken like this: Game time reported incorrectly for tournaments without 24hr playing time. Thanks for the fixes, but no thanks for not finishing the job.

[dschingis27]

I noticed that the tournament pages of completed tournaments have auto-focus on the Tournament Status, which is the final ranking in that case. I think it would be extremely useful to have the same auto-focus on Tournament Status in ongoing tournaments, too! The main use case for checking pages of ongoing tournaments is to check the standings. Currently, users have to scroll a lot each time they want to do that.

Think of all the scrolling that could be saved! You can vote here: https://boardgamearena.com/bug?id=216081

Other than that, as pointed out by Meeplelowda and others, there are still extremely annoying if not tournament-breaking bugs still existing. The top two annoying bugs are certainly these two, they also get frequent mentions in the forum:
- Game time reported incorrectly for tournaments without 24hr playing time
- Players Who Tie In A Tournament Should Advance Randomly, Not By Account Age

The latter problem still existing is completely contradictive to the goal of BGA to be very friendly to new users. Newer users are extremely annoyed by this and there are complaints all over the place in the forum.
https://boardgamearena.com/forum/viewtopic.php?t=48539
https://boardgamearena.com/forum/viewtopic.php?t=48450
https://boardgamearena.com/forum/viewtopic.php?t=48762

Please, please, please, fix these.

[RazorOz]

I noticed that the tournament pages of completed tournaments have auto-focus on the Tournament Status, which is the final ranking in that case. I think it would be extremely useful to have the same auto-focus on Tournament Status in ongoing tournaments, too! The main use case for checking pages of ongoing tournaments is to check the standings. Currently, users have to scroll a lot each time they want to do that.

Think of all the scrolling that could be saved! You can vote here: https://boardgamearena.com/bug?id=216081

Other than that, as pointed out by Meeplelowda and others, there are still extremely annoying if not tournament-breaking bugs still existing. The top two annoying bugs are certainly these two, they also get frequent mentions in the forum:
- Game time reported incorrectly for tournaments without 24hr playing time
- Players Who Tie In A Tournament Should Advance Randomly, Not By Account Age

The latter problem still existing is completely contradictive to the goal of BGA to be very friendly to new users. Newer users are extremely annoyed by this and there are complaints all over the place in the forum.
https://boardgamearena.com/forum/viewtopic.php?t=48539
https://boardgamearena.com/forum/viewtopic.php?t=48450
https://boardgamearena.com/forum/viewtopic.php?t=48762

Please, please, please, fix these.

They should just put an option for tournaments of "all games play to conclusion". We know it's already coded because Heat, Formula D etc. have this coded already for all games, and would be a much better for option for the vast majority of games. Because while random is better than how it is now, it's still lame, and will lead to many complaints of I was going to win, but x quit on the last turn and I went out. It's the only real way I can think of to fix the issue while being somewhat fair (particularly because everyone would know where they stand before it starts).

[blockmonoid]

Here's another change that was better previously:
In a single or multiple elimination tournament, you click on Registered Participants in the Tournament State box, it shows all the participants, with the eliminated ones greyed out, just like before. However, in the old site, the participants who are still "alive" appeared at the top of the list, so you could easily assess who was still left in the competition. In the new version, the participants are listed in some order (random? order of registration?) and so you have to click and scroll to try to find everyone who is still alive. Very tedious to find out this information, especially because (as has been mentioned before) that Tournament State box involves so MUCH clicking to "scroll" through the its contents.

[Meeplelowda]

After a flurry of fixing things that were working just fine and got broken by the tournament pages overhaul, has BGA quiet quit this task? There are still things that are broken like this: Game time reported incorrectly for tournaments without 24hr playing time. Thanks for the fixes, but no thanks for not finishing the job.

OK, this is not a case of people saying something is an "easy fix" when it would take days of a developer's time. This issue is literally a case of going to the line of code that assigns a value to the variable that defines how much time is on each player's clock (let's called it playerClock) and setting up a conditional statement that if a game has playing hours set (for which there must be a flag somewhere in the code) then "playerClock = playerClock * 0.5," or the equivalent. The only issue may be that for some reason the variable acting as the flag that determines if a game has playing hours only has a local scope and the code that assigns a value to playerClock can't access it. In that case, this wasn't a simple omission. It was a complete failure to understand how playing hours worked previously when implementing the new framework.