Helpful Suggestions for smooth OOPs

Omac's OOPs are terrible.They have changed start strategies for the game.Attacking/warring OOP are a thing of the past due to incompetence.You would be best off to explore/dice till the cow's come home with no defense because of the net difference factor.

I would suggest a one week downtime between ages.That way you can have a test THE start at a faster tick,either ever 15 minutes or every 1/2 hr to see the bugs and fix them as you go.

Now if you find the "Oops something went wrong" error when you start the real OOP/start after fixing "BUGS"you then obviously know by the process of elimination that the server/code is a piece of dung (which it is btw)

- Schedule end of freeze time on date when someone is there to handle problems when they occur
- Same for end of protection

- Data validation.
- Data validation.
- Set each new age up on a separate server before it begins and test it with fast ticks.
- Data validation.