Sorry that's my fault :( We deployed and tweeted about our 1st version an hour before the code freeze and some guy came on and trolled the server by changing instruments and effectively froze all the connected clients. After seeing that, I whipped up a rate limiter in the final minutes that disconnects people based on a crude warm up/cool down system, but set the limit a bit too strict.

sorry dannytatom, we put a rate limiter at the last second to keep our server from getting overloaded and it needs a little adjusting. if you try not to click around too fast it shouldn't be too big of a problem.

All good, was just confused as to why it was happening. It's worse because what I was doing would start sounding awesome, then I'd realize nobody had been doing anything in a while, only to find out it was because I had been disconnected minutes earlier and was playing alone. :p