@Farbs, just fyi the guild thing stopped recording new battles a couple days ago. (No rush, but just in case you hadn't noticed yet.) And unlike last time, I'm sad that it missed my stunning series of wins over the last two days...
It's back! Over the next few hours it should pick up all the battles that it missed. Performance will be a bit chuggy in the meantime. Thx to j-wiz for rebooting the API service. EDIT: It has caught up on all the missed battles now. I wouldn't normally bother reporting that, except that 99K ARE NOW IN THE LEAD! HA!
@Farbs, there's something strange about @hatchhermit 's account, in that he doesn't appear in the roster for Double Rainbow and I can't pull up his profile, although there is a line in the DR guild history that says he was successfully registered with the guild and the guild size is one larger than the number of entries in our roster. (Not urgent, but something to poke at sometime...) EDIT: I suspect the problem may be that @hatchhermit may have never played an MP ladder match?
So what's up with the meta site showing two instances of the same game lately? It's also seemed very laggy, might be related. It might actually be counting those games actually... uh oh.
Erp, yeah it almost certainly is. There's supposed to be some code in place to prevent concurrent updates, sounds like the site is seeing more use and this code is failing. Will check it out.
If the game becomes self aware, it should develop feelings. If it does, I want to torture the RNG slowly and repetitively. PBAB.
Hmm. I suspect the culprit might be the API response time, which is currently somewhere over a minute. My site was configured to check the API for new battles no more often than once every minute, however it assumed that it could collect all the battle data within that time period. Otherwise a subsequent page request could re-trigger the battle scraper before the last one completed, thereby scraping some battles multiple times. Urgh. For now I've increased the minimum battle scrape time to 10 minutes, so it can take up to 10 minutes for your battle results to appear. This isn't great but should be more stable. Hopefully we can find a way to improve the API performance too.
I found a way to turbo-boost the API, hotfixed it, and cranked the battle scrape period back up to 1/minute. So battle results should be much more recent now, and [META] shouldn't lag as much when it scrapes on a page load. Now, back to work...
Whether Turbo-Boost has any real meaning here or not, bonus points to Farbs for sounding Game-Techie.
