Earlier today the BKG California server crashed. It's an Amazon EC2 Linux instance that I've paid for for a couple years now, but for whatever reason after rebooting it I was no longer able to connect with it remotely. I fussed with it for a good five hours, but Amazon's 1700 different features can be pretty unfriendly and ultimately was not able to get it back in working condition for some reason.
To replace it I've purchased a Digital Ocean server that is faster, has way more disk space, and is half the price. It takes a little work to get a fresh Linux server setup, but it's up and running a new world now, and I was able to connect to it just fine. It is set to reboot the server thread every 12 hours, and I'm going to try and setup some monitoring so that it can reboot the whole OS if it somehow gets stuck in a loop as it seemed to earlier today on the Amazon server. If that happens again tracking down the cause of the loop will be my top priority, but as I can't even access the Amazon server anymore I can't look at any of the log files to try and debug what went wrong ːsteamfacepalmː
Sorry for the loss of data for everyone that was playing on the BKG server. Hopefully the new server will be easier to manage!
I've got a few bug reports involving multiplayer resources incorrectly respawning on clients, rare cacti not loading properly, and some trouble with transferring items in and out of bags via the transfer buttons I will be looking into Monday (tomorrow for me) morning.