For enemy temples during Server War, troop power must meet a minimum before occupation time and score begin to count. More power improves the score only up to a stated cap, while uninterrupted occupation can add large time bonuses at defined milestones.
Evony's Version 5.26.0 announcement states that occupying troops in enemy Temples need at least 100M power to count occupation time and earn Server War score. Score growth stops increasing after the power limit, which was raised to 500M. It also lists a minimum occupation score of 600 and maximum of 10,600. See the official SvS Temple rule update.
The Three Numbers to Remember
100M minimum power
Below 100M power, the announcement says occupation time and Server War score do not count. This is an eligibility threshold, not a safety recommendation.
500M power cap for score scaling
Once troop power reaches the limit, adding more power no longer increases score earned per second. Extra power may affect survivability, but it should not be sent under the assumption that it keeps increasing the scoring rate.
Continuous occupation milestones
The official rule adds occupied time immediately after continuous occupation of 30, 60, 120, or 240 minutes. The added time is 5, 15, 60, or 160 minutes respectively. If troops leave the Temple in any way, the continuous occupation is broken.
Plan the Occupation
- Confirm that the target is an enemy Temple during the active Server War.
- Build a march that clears the 100M threshold with a margin for any power changes.
- Decide whether the goal is short scoring, a milestone, or denial.
- Coordinate reinforcements and monitoring before occupation begins.
- Track the continuous timer from the start.
- Do not recall, replace, or otherwise remove the occupying troops without understanding that continuity will be lost.
- Reassess after each milestone rather than sending excess power automatically.
Milestone Example
A team plans for 60 minutes of uninterrupted occupation. Reaching 30 minutes adds 5 minutes, and reaching 60 minutes adds 15 minutes under the published rule. If the troops leave at minute 58, the 60-minute continuous milestone is not reached, even if another march enters immediately.
This is why continuity management can matter more than simply increasing the original march above the score-scaling cap.
Common Mistakes and Diagnosis
- Sending under 100M: The occupation may not count for time or score.
- Assuming more than 500M keeps scaling score: The published power limit caps that increase.
- Swapping marches casually: Troops leaving break continuous occupation.
- Planning a milestone without coverage: Assign monitoring and response roles first.
- Treating score thresholds as combat safety: Enemy action can still remove the march.
Quick Checklist
- Active Server War confirmed.
- Enemy Temple confirmed.
- Occupying power at or above 100M.
- Score-scaling cap understood.
- Milestone target selected.
- Continuous timer monitored.
- Recall and replacement risks communicated.
FAQ
Does a 99M march earn occupation score?
Under the published Version 5.26.0 rule, troops must have at least 100M power for occupation time and score to count.
Does 700M power score faster than 500M?
The official note says score earned per second no longer increases after the power limit, which is 500M.
What breaks continuous occupation?
The announcement says that if the troops leave the Temple in any way, it will not count as continuous occupation.
Are the temple blessing effects the same as occupation scoring rules?
No. Blessings describe account effects from the temples, while these rules describe Server War occupation thresholds, score, and continuity.