In my opinion, this problem is not caused by treating temples like ghost towns, it is simply a technology limitation.
What about the delayed processing of the reports?
In Germany we had a delay of 20 hours when attacking the Olympus. However, it would have been even more if the developers hadn't intervened and canceled some commands.
Has this problem also been resolved?
A simple way to prevent this massive amount of spam would be to treat the temples not like ghost towns, but like "normal" cities, where there is a minimum number of troops sent. If necessary, this quota should even be increased (for example that an order (attack and defense) must occupy at least 200 farm places).
So you already have solutions for this problem, but you were not able to solve this problem?Solutions for problems like this one exist, although they can be really hard to implement.
You can always cause a delay if there's a lot of movements, no matter if it's 1 lightship or the whole nuke. It does not apply just to temples, but also to normal conquests.
Why would it be harder at the start of the server? At the beginning of the server no temples that have already been conquered are attacked anyway. It is easier then to simply conquer new ones, or you wait until you have more troops, then it will be no problem either.Your solution to increase the minimum population requirement per attack is a double-edged sword. I agree that the solution would help in the late game (World wonder sieges, Olympus, etc.), but it would also make the game a lot harder from the start of a server.
About 5000 attacks and 5000 supports were timed on the Olymp.What exactly did you do to halt an entire server for 20 hours?