Discussion in 'Guilds' started by Flaxative, Jan 6, 2015.
If he doesn't I know his Steam account where you can talk to him worst case scenario.
Congratulations to the top guilds of July! Your pizza has been sent.
Good luck everyone in AIGUST!
Whos top of Aigust ist still open, but scores might need a closer look this time around, given the meta seems to favour some more then others.
I'm not sure I follow. Are you saying that some players figured out how to play better on the maps this month than others?
It looks to me like some matches are being counted multiple times.
Oh, I'm guessing that happened because the API went down briefly yesterday. @Farbs
Certainly was not just limited to the matches pictured. But in the overall guild (match) history the "double ups" are scattered all over the place (not necessarily chronologically next to each other like that screenshot). Gonna take some work to find them all.
Thanks for the heads-up.
Has this substantially changed any guild's ranking for the season? If not I'm tempted to leave it. This bug has been around since the meta site began, and seems to have spiked a little yesterday with the API and forum mishaps, but doesn't selectively favour anybody.
Also I have absolutely no idea how to fix it. So, there's that
For the carpets those points could mean the diffrence between rank 3 and 4
I've been receiving some intricate messages about which guild should really be in what place this month due to the API bug.
Rather than replying to the concerned parties piece meal, here is a short statement on the situation.
As @Farbs has said, this bug has been around since the dawn of guilds. It has affected everyone from the beginning, in tiny doses here and there. We have never manually corrected for it before, and we won't start this month. Maybe a guild's rank is directly affected by one occurrence of the bug this month—but also, maybe that guild has benefitted in previous months (or maybe even earlier within the same month) in the opposite direction. It doesn't make too much sense for us to look at just one hour of match results and try to adjust the final standings by so many points.
Obviously, we wish that there were zero bugs! But in the interests of keeping things running smoothly, until and unless we are able to prevent the bug from occurring in the future, whatever standings Farbs's site produces—however minorly flawed—will stand.
Barring blanket outrage, I will distribute prizes in about a day.
I hadn't looked at each guild's August 29th results, but given the fact that the hiccup was big enough to skew the end results for multiple guilds, I think that more than warrants the need to recalculate for August 29 during that 2 hour hiccup window.
Along with that, Sucre's win streak needs adjusting. For those of us really competing for top honors in those listings, a bug shouldn't result in the best ever win streak.
Sucre won 12 free games and 30 gp during the hiccup, pushing his win streak to 50! and ultimately giving his guild enough of a boost to win, since the hiccup occurred with only 2 days left in the season.
It's not really a big deal that the bug exists. I'm not looking for anyone to fix it. All of the guild players that are really competing are watching the meta site closely enough that we know when something major happens that can have an impact on the month's outcomes.
It's easy to calculate the difference. I've already calculated the difference for the 1st and 2nd place guilds.
If Kraken won due to a hiccup, we would simply not accept the championship.
Finally, Kraken is more than willing to forgo prizes in return for a readjustment of the scores this season.
Nah, sucre won 50 games in a row.
Oh good. So, the Braves did accomplish something this month on their own merit. Good work, Sucre!
You could just have left it at
The whole "this issue got rich history and touched all our lives" thing is a head-scratcher.
Dammit. I left my outrage blanket at my last protest.
Good luck everyone in Septorigin!
Just fyi, this rotation has 5 maps, the meta site is missing Dungeon.
Separate names with a comma.