New features and refactoring are fine, Tom, but please keep in mind that breaking the game is worse for player retention than any shenanigans us players can do. Quite a few islands were broken for a period of days.
What we really need is a robust testing system, where features can be tested without risking breaking every other island. Maybe the devs can get their own private island to play around in?
Because just "turning on a feature and hoping it works" does not seem to be working. 
That's not how we work, and we do have a testing server.
The issue we are having now is that we are using an entirely new database layer, Doctrine ORM. It has many "features" that come unexpected to us, such as failing the entire turn on minor errors where the old code only failed that particular update and else continued just fine. Both has its pro and cons. The advantage of the new system is that once we have adapted our code structure to it, turn runs will be monolithic, meaning that it either succeeds completely, or fails completely. Which means in the case of failure we can fix the error and re-run it, something we can't do when the turn was a partial success.
But as De-Legro already wrote, while we try to test changes on the dev server, there simply is no way to test the actions of several hundred players. We push things live when we believe they will work, but sometimes we get nasty surprises.
And yes, I realize that breaking the game sucks.
