BRIKWARS is the plastic-brick tabletop wargame that throws the peaceful worlds of construction toys into wanton mayhem!

Bring and build your own armies, vehicles, and monsters in an all-out war for deconstruction toy glory, with a robust system to incorporate whatever you create. If you can build it, you can bring it to battle in BRIKWARS!
Maintenance
Mike - March 31, 2019 - Maintenance

Good news everyone! Following a minor server migration disaster this week, I’ve done a clean reinstall of every application on the site and performed some kind of crazy SQL wizardry to duplicate all the content from the previous versions into the new databases that were not at all designed to accommodate them.

Everything is now SSL secure and PHP7 compliant, so you can expect everything to run faster, more smoothly, and more reliably than on the old PHP5 machine that’s been struggling to keep up with our nonsense for the last decade.

Mike - July 16, 2018 - Maintenance, The BrikWars Wiki
The BrikWiki is down for the time being due to a memory leak in the database – we’re currently backing everything up and looking into some fixes.

UPDATE, July 17: The wiki is now fixed!

And we all learned an important lesson: when GoDaddy tech support tells you they’ve restored functionality, don’t believe them. I could have saved hours if I’d just taken the reasonable step of checking for myself whether they were telling the truth or not. The original database is still disabled, but we were able to copy the data to a new non-disabled database and everything’s working fine again.

For curious googlers with the same problem: there’s a bug in MediaWiki that adds a new entry to mw_objectcache on every pageview, with no expiration date, even when caching is turned off. Our mw_objectcache had grown to a gig in size, setting off automated database disabling.

Regardless of your caching level, you can safely empty the entire mw_objectcache and let MediaWiki rebuild whatever parts it needs – unless GoDaddy has already disabled your database, in which case you can make a backup of the old database, copy it into a new one, and redirect your wiki to it.