Hello all, we’ve unfortunately hit a bug that is serious enough to be game breaking. I have since fixed the bug, but enough damage has been done that we are going to reset the round.
Thankfully, the round only just started recently, so a reset although annoying isn’t horribly disruptive.
We’ll be ending #triangulum-31 early, calling it a “lost round”, and setting up #triangulum-32.
Times are as follows:
| Time | Event |
|---|---|
| 2022-08-04T14:00:00Z | Tri 31 ends |
| 2022-08-04T14:00:00Z | Tri 32 opens for votes |
| 2022-08-05T14:00:00Z | Tri 32 is created, pre-round planning begins |
| 2022-08-06T14:00:00Z | Tri 32 round starts |
| 2022-08-29T14:00:00Z | Tri 32 ends |
We’ll be skipping the normal queue signup phase so that the current players can jump right into voting and we can keep things moving.
Speaking of voting, a silver lining here is that it will coincide with the vote update change that I’ve recently finished:
This will help us avoid surprising results, which players have expressed frustration about with family size in particular.
That does mean that Tri 31’s 3 families of 12 will be up for a revote, along with the other options.
I apologize for not catching this bug while we tested our recent upgrade. Thank you all for your patience and understanding. I will post more details about the bug itself in its thread soon for anybody who is interested.
Feel free to ask any questions below if you have them.