Direct answer
What should you do?
Alliance events reward preparation before power. Confirm the event rules, objective, participation window, rally leader, reinforcement plan, and recovery limit before deploying; then give each member one clear role.
Key takeaways
- Read the current event panel because loss, scoring, and timing rules can change.
- Assign rally, reinforcement, defense, scouting, and reserve roles before conflict starts.
- Measure success by the shared objective, not by isolated battle reports.
1. Prepare one page of shared information
Before Stronghold Fighting Day, cross-server war, demon defense, cave exploration, or a boss rally, alliance members should know the start time, objective, rally lead, required formation, and stop condition. A short plan prevents more losses than a long discussion during the fight.
Use the in-game event panel as the source of truth. This guide explains preparation; current scoring, damage, registration, and participation details must be verified in game.
- Post the event time in the alliance's main time zone.
- Name the rally lead and backup.
- State whether the objective is points, occupation, defense, rating, or completion.
2. Assign roles that match availability
Not every member needs to lead a rally. Reliable reinforcement, defense, scouting, and reserve players can determine whether the alliance holds an objective after the first engagement.
Match roles to online time and recovery capacity. A strong account that disappears halfway through the window may be less useful than a smaller account that can reinforce consistently.
- Rally lead: sets target and timing.
- Reinforcement: keeps key positions functioning.
- Reserve: responds to a second objective or failed push.
3. Review the shared outcome
After the event, review whether the alliance met the objective, whether calls were understood, and where recovery became strained. Avoid reducing the discussion to the largest individual battle report.
Keep one change for the next event. It may be a clearer registration reminder, a different rally window, a formation requirement, or a stricter retreat call.
- Record the first coordination failure, not every small mistake.
- Confirm which formations performed their assigned role.
- Update the next event note while the result is still fresh.
Decision table
| Event type | Primary planning question | Useful role |
|---|---|---|
| Stronghold objective | How will we occupy and then hold? | Rally, reinforcement, reserve |
| Cross-server war | What is the scoring and recovery limit? | Target caller, defense, rotation |
| Demon or boss event | What timing and formation completes the shared target? | Rally lead, consistent joiners |
| Team cave | What raises completion or rating? | Formation specialist, schedule coordinator |
Frequently asked questions
Do all alliance events use the same loss rules?
No. Verify the current event help panel before deploying.
What should a smaller account do?
Follow the event's permitted roles and alliance instructions. Reinforcement, timing, reserve coverage, and reliable participation can be valuable.
How should an alliance review an event?
Compare the shared objective, communication, formation fit, and recovery pressure, then choose one improvement for the next run.
Official sources and scope
This guide is based on current official product information and product-team review. Exact values, event rules, and unlock requirements can change; verify time-sensitive details in the live game.
Continue in game
Play Alliance at War
Use the guide as a decision framework, then confirm current values and rules in the live game.