BuzzerBeater Forums

Bugs, bugs, bugs > Rivals, again

Rivals, again (thread closed)

Set priority
Show messages by
This Post:
00
58909.1
Date: 11/18/2008 1:37:02 PM
Overall Posts Rated:
3737
Since the original bug thread was extremely prematurely closed (my longstanding opinion [and once, policy]: never close a valid, non-duplicate bug thread... it achieves nothing useful), a new rivals issue.

According to the blue box, the rivals updates are supposed to be done by now. In fact, they do seem to be mostly done. If you look at Canada's top division, 3 of the 16 teams (including mine) now have no rivals at all. The other teams appear to have new rivals.

My guess is that is an uncaught error in the rivals processing, and not just me being impatient.

This Post:
00
58909.2 in reply to 58909.1
Date: 11/18/2008 1:43:24 PM
Phoenix_Suns
III.5
Overall Posts Rated:
176176
In my league, it´s done, but, same as last season, some teams are rivals of more than one team, some teams are no rivals at any team. This disadvantage should again be solved.

This Post:
00
58909.3 in reply to 58909.2
Date: 11/18/2008 1:46:33 PM
Overall Posts Rated:
3737
That's probably something for a separate thread, in the Suggestions forum. Nothing to do with this bug report.

This Post:
00
58909.4 in reply to 58909.1
Date: 11/18/2008 1:53:23 PM
Overall Posts Rated:
3737
Looks like the outstanding Naismith teams now have rivals.

This Post:
00
58909.5 in reply to 58909.1
Date: 11/18/2008 1:56:41 PM
Overall Posts Rated:
506506
Sorry if I closed that thread too early, but patience really is the keyword during offseason processing.

This Post:
00
58909.6 in reply to 58909.5
Date: 11/18/2008 1:59:47 PM
Overall Posts Rated:
3737
When it comes to new features (this is the first off-season rivals creation, I think), I'm less likely to be patient and more likely to believe in bugs. Especially when it's an hour past the stated completion time.

In any case, whether it was just a matter of the update still being in progress, or there being a bug fixed, I'm glad it's fixed.

And, from my position, it's not that you closed the thread too early, it's that you closed it at all.