What it is
An epic run is a player-organised session in which clanmates agree when to attack a live epic squad. The game schedules the host tournament; your officers schedule the clan's run. Clan CP runs are also player-organised, but their agreed player battles are a different activity from fighting an epic.
A run has no game tournament, reward ladder or chest of its own. Its battles follow the host's rules, whether the organiser chooses Armageddon, Doomsday or another available epic.
That matters when you write the invitation. Name the host and target, say when attacks should arrive, and explain whether members are sending separate attacks or joining a group action permitted by that event. Calling everything a raid leaves room for expensive misunderstandings.
When it runs
There is no game-wide calendar for your clan's epic runs. Pick a session within the host's live window, using the calendar to find the host and its current countdown to confirm availability.
State the agreed time in UTC and distinguish arrival from departure. Members at different distances may need to leave at different moments to meet the same arrival instruction. Publish a separate assembly deadline if your chosen action has a rally phase.
Avoid promising a repeating run independently of its host. A standing clan appointment can be useful, but it still needs a live target and a permitted attack format when that appointment comes around.
Who can take part
The official epic-battle rules give different commander restrictions for different hosts. Check the current event instructions before assembling an army.
| Host | What its rule permits |
|---|---|
| Doomsday | A maximum of 1 captain |
| Hellforge | A maximum of 1 captain |
| Arachne's Swarm | All 3 Captains |
| Armageddon | Your Hero only |
| Shadow Invasion | Your Hero and Captains together |
Your division normally depends on your Hero level, unless the event specifies otherwise. Personal-goal difficulty and reward size depend on army level. An organiser's invitation does not replace either rule.
A member who can join the planned session may still have a different personal target from a stronger clanmate. Ask members to follow their own event screen rather than promising an identical milestone to everyone who attends.
How it works
Agree the action before agreeing the minute
Write the target and permitted commanders into the same instruction as the arrival time. Check that the target is still available before asking members to commit. For a follow-up wave, issue a fresh instruction after assessing the previous battle.
The official scoring floor is simple: an attack with 0 monster kills earns 0 points. More kills produce more tournament points, Valor points and experience. Attendance alone therefore cannot establish a member's score.
Keep threshold claims provisional
Some organisers describe an epic as a shared points pool that releases chests at thresholds. No official source confirms that model, its spacing or a fixed chest total.
The official epic-battle article doesn't describe a shared points pool, chest thresholds, their spacing or the chest total. Only watching a run in the game shows them.
Treat figures an organiser supplies as their estimate. Do not turn them into a guaranteed chest calculation or tell members that a synchronised wave has a documented claim on the next reward.
Separate the battle from chest delivery
The official delivery article says rewards from a heroic group march reach its participants after disbanding and the return of reinforcements. Its wording matters: it does not establish an identical delivery rule for every epic attack format.
Delivery timing and who receives the credit aren't published for every epic host and attack format; the official delayed-delivery article describes heroic group marches. Check the format you choose in the game.
For that reason, keep the organiser's attendance list alongside chest activity. A delayed gift or a shared march reward should not be used to rank individual damage.
Rewards
The run adds no reward of its own. Read personal goals, currencies and chest conditions in the host event. For the details of particular hosts, see the Armageddon guide, Doomsday guide and Shadow Invasion guide.
As an example, Fire Hydra Chest is the chest of Armageddon (game catalogue): a host's reward, not one for signing up to a player session.
| Reward | Chance |
|---|---|
| Reset Talent points | 13.6% |
| Gold | 11.6% |
| City teleporter | 9.5% |
| Lumber | 7.5% |
| Stone | 7.5% |
| Iron | 7.5% |
| Epic Tar | 2% |
| Tar | 1.4% |
Each percentage is the chance of that reward once you open the chest, not the chance of earning it or a share of the damage.
Once a gift appears, the Gifts rule allows 20 hours to open it. Check that deadline even if the organised session has already ended.
A plan for your clan
Common mistakes
- Treating a clan appointment as a separate tournament with its own rewards.
- Reusing the previous host's commander instruction.
- Giving a departure time when the organiser actually means arrival.
- Promising chest thresholds that remain unverified.
- Treating a shared or delayed chest as a measurement of individual damage.
FAQ
Is an epic run an official game event?
The epic host is official. The session your clan schedules against it is player-organised, just as a clan CP run is player-organised.
Can everyone send all their commanders?
No. The host restrictions differ. Use the table above and check the live event before sending troops.
Does being present guarantee points?
No. The official epic-battle rule requires monster kills. Attendance confirms the member joined the plan, not that their attack scored.
Does the run have its own chest?
No. Any chest belongs to the host's rewards. The example percentages apply only to that host's chest.
Why keep an attendance list if chest activity is available?
Attendance, battle contribution and chest delivery answer different questions. A fair session record preserves those distinctions instead of converting chest counts into damage claims.
Sources
- TB Clan Tools event notes
- Epic monster battles ·
- Clan gift deadlines ·
- Heroic group-march chest delivery ·
- Example host chest, not a separate epic-run reward
First published · Updated
