Re: New tournament summary page !!
Posted: 24 February 2026, 19:32
The worst thing that ever happened to BGA. Tournament basically died for me
I love playing tournaments but the number of tournaments has dramatically decreased, I have never seen so few tournaments in my filter (not even in the summer holiday, while I play a lot more different games now compared to last summer).
I've only posted in the thread announcing the new tournaments lobby until now because this one seemed redundant (and the community liaison is actually participating in the other thread). But this statement reminded me of my prophesy nine months ago in the Elo Systems Update megathread:
Now that time has come. This is why I was sympathetic to people making reasonable arguments in the megathread who felt they weren't being listened to and were met with silence even if I didn't really care about the issue (not to say that you aren't sympathetic).Meeplelowda wrote: ↑25 May 2025, 22:14 These changes have not affected my life in the least, so I am not personally invested in what they do or don't do on this issue. But eventually they are going to screw up something major that I do care about and all evidence suggests it is going to be handled the same way.
I'm absolutely sympathetic - my point was more that I haven't been playing tournaments for a while, so it's not affecting what I do on BGA right now, but if anything, the discussion here was making me feel like going back to investigate tournaments at present would be a frustration at best. My other point was, I feel like I've seen this pattern before - where they release some new feature to a group of testers for a quite short period, get a bunch of practical feedback, ignore it and release anyway. I'd like to say they're looking for actual (major UI/implementation-breaking) bugs, although the debacle with tiebreakers suggests they weren't even trying to make it bug free. So I'm very confused why they even put it before testers.Meeplelowda wrote: ↑25 February 2026, 23:49I've only posted in the thread announcing the new tournaments lobby until now because this one seemed redundant (and the community liaison is actually participating in the other thread). But this statement reminded me of my prophesy nine months ago in the Elo Systems Update megathread:Now that time has come. This is why I was sympathetic to people making reasonable arguments in the megathread who felt they weren't being listened to and were met with silence even if I didn't really care about the issue (not to say that you aren't sympathetic).Meeplelowda wrote: ↑25 May 2025, 22:14 These changes have not affected my life in the least, so I am not personally invested in what they do or don't do on this issue. But eventually they are going to screw up something major that I do care about and all evidence suggests it is going to be handled the same way.
Given your subject matter expertise, I value your educated guesses about their motivations. The weird thing about the tiebreakers is that they seemingly wanted to take tiebreakers away entirely at first and released the new framework without tiebreakers. It was putting them back that introduced the bug, but that happened after the new framework went live, so no one could have caught it during testing.nik592 wrote: ↑26 February 2026, 05:18 My other point was, I feel like I've seen this pattern before - where they release some new feature to a group of testers for a quite short period, get a bunch of practical feedback, ignore it and release anyway. I'd like to say they're looking for actual (major UI/implementation-breaking) bugs, although the debacle with tiebreakers suggests they weren't even trying to make it bug free. So I'm very confused why they even put it before testers.
I mean, I get that there's a degree of them putting in the best solution for their whole user base, not just a vocal minority. I've seen customers of our own product complain that they can't believe we haven't fixed bug X (because they're the only one who really cares) or why we've changed a process to work a different way. But I know there's a lot that goes into considering the best choices - and our customers don't really have a good handle on what other customers are saying. But BGA doesn't have a dedicated support team who are talking to customers individually (as we do), I highly doubt they're doing market research to drive sales and comparing to other similar providers (as we do), I don't believe they run surveys and user conferences to get feedback on what people want. This forum (and bug reports) is likely the main place they're getting that info. And we also release early access releases to testing groups, but their feedback is noted and valued, even if some of it is tabled for a down the track fix. This feels like at least the second time where testers were engaged by BGA and then ignored. So why even engage them, unless you're just looking for major bugs that make the whole system fall over?Meeplelowda wrote: ↑26 February 2026, 05:55 Given your subject matter expertise, I value your educated guesses about their motivations.
Ah, that makes sense. It seemed like an odd bug to have been left in there. That said, removing tiebreakers also seems like lunacy - ties are going to be a thing, and need to be resolved (I guess even if that resolution is to share placings, but then you have things about dividing XP awards between multiple players, etc.).Meeplelowda wrote: ↑26 February 2026, 05:55 The weird thing about the tiebreakers is that they seemingly wanted to take tiebreakers away entirely at first and released the new framework without tiebreakers. It was putting them back that introduced the bug, but that happened after the new framework went live, so no one could have caught it during testing.
As I said in the main thread, this decision reeks of being made by someone who doesn't actually play and understand round robin and Swiss tournaments. But they asked for feedback from people who DO play them, and I know several of us noted the absence of tiebreakers being visible.
Perhaps not entirely, but it seems that issues were raised by the testers and not fixed before the release. Then non-testers started pointing out the same issues, and some of them asking how this got by the testers? To which the testers very fairly respond that it didn't - they reported it, but it was released as is. That's ignoring (on those issues anyway). Just because they take on board some feedback doesn't allow them to ignore other valid feedback. At the very least, they need to be explaining the rationale behind decisions to leave work unfinished.dschingis27 wrote: ↑26 February 2026, 10:34 To be fair, BGA did not ignore the testers, the testing-development cycle was helping and improving the module but at some point they just stopped and released it with unresolved core issues.