Part of the Events Series:
- Events Hub: Plan overlapping scoring windows.
- Alliance Hub: Coordinate with officers.
Quick Answer
Accept an Alliance Throwdown task before doing the activity it scores, and choose one you can finish within its timer. A canceled or failed accepted task can consume an attempt. Optimize completed points per attempt rather than choosing the largest number on the board.
Throwdown is a recurring alliance task event. Established rules use a six-day task period, with alliance tiers affecting attempts and rewards. State progression changes the task pool; use your board's counters for the current session.
Overview
Your completed tasks contribute toward alliance progress, while reward eligibility also depends on the session's personal requirements. Check both before assuming you qualify for every crate your alliance unlocks.
The documented entry requirement is an alliance with at least 15 members at HQ 10 or above. Join the intended alliance before taking tasks or claiming rewards elsewhere. Moving alliances after participation can leave your points behind and prevent further task-taking in the new alliance.
Understand the Task Types
| Type | What to check | Coordination |
|---|---|---|
| Normal board task | Objective, point value, deadline and remaining attempts | R4/R5 manage refreshes of shared tasks |
| Exclusive or personal task | Bonus value, required items and personal refresh timer | You can manage your own options |
| Custom task, where available | Progress milestones, claim button and daily reset | Confirm whether it allows partial point claims |
Newer boards can include custom tasks with progress-based claims. Older explanations show only normal and exclusive tasks. Do not apply the older board's attempt or bonus limits to a different interface.
Compare tasks of the same cost before calling a bonus task better. A higher multiplier attached to a much larger requirement can be worse for your inventory.
Task Selection by What You Already Have
| Available activity or stock | Task worth checking | Main constraint |
|---|---|---|
| An active alliance running fiends | Eligible rally or fiend task | Stamina, rally availability and the exact objective |
| Marches returning during your play window | Gathering task | Whether progress is credited on return and which resources count |
| A planned troop upgrade | Troop Power task | Power gained, resources and completion time |
| Research or construction nearly ready | Compatible speed-up or growth task | The task may score items used rather than completion |
| Saved hero or machine materials | A matching development task | Item name, rarity and accepted currency |
| A purchase already budgeted | A qualifying purchase task | Pack eligibility and required purchase sequence |
For fiend tasks, use the PvE rally guide. For troop tasks, distinguish training from upgrading. Never assume a task counts both in the same way.
Calculate Your Ceiling Before Accepting
Write down the task requirement, the eligible stock you can spend and the time left to play. Include resources needed to start the upgrade, not just the speed-ups needed to finish it.
Illustrative planning example: if one task awards 200 points but you only have half the required material, it is not automatically better than a 150-point task you can finish. Those numbers are examples, not a published Throwdown points table. An incomplete high-value task may waste both time and the attempt.
Once accepted, do a small eligible action and verify that progress moved. Then commit the remaining stock. This is especially useful for currencies with similar names, such as Plasma Cores and Polymerized Plasma, and for tasks based on the highest equipment score rather than every item upgraded.
Officers: Keep the Board Usable
Ask members what tasks they can complete, and keep a short request list. Do not refresh a useful task immediately after someone asks for it. Replace tasks the roster cannot use, while leaving a range of achievable choices for different account sizes.
Standard tasks historically refresh on a longer timer than personal options. Read the current timers before mass-deleting the board near the deadline. A clean board with nothing available is worse than a modest task a member could have completed.
Stack Events Without Stalling Progress
Check Survival of the Fittest and SvS preparation for a genuine overlap in both time and eligible activity. An event that starts next week is not an overlap.
Keep normal building and research queues moving. Save discretionary materials and speed-ups when waiting creates a useful scoring opportunity; do not postpone a major unlock for days solely to earn a small task reward.
F2P and Spender Priorities
F2P: favor tasks supported by normal play and materials already reserved for upgrades. Check the free extra-attempt allowance before paying Biocaps for another attempt. Buy an attempt only when you also have an achievable task for it.
Spenders: select a purchase task only for a purchase you already intend to make, and verify the pack qualifies. An unnecessary bundle remains an expense even when it completes a task.
Common Mistakes
- Spending first and accepting afterward.
- Canceling a task without accounting for the lost attempt.
- Choosing a large task that cannot be finished before logging off.
- Refreshing shared tasks another member is preparing to take.
- Spending next event's entire reserve for a minor ranking increase.
FAQ
Who can refresh Alliance Throwdown tasks? R4/R5 manage normal shared tasks. Personal or exclusive options can be refreshed by their owner under the current board rules.
Do I lose an attempt when canceling? Accepted normal challenges can consume the attempt when canceled or failed. Read the confirmation before abandoning any task type.
What are the best F2P tasks? Tasks that match activities and inventory you already have: feasible gathering, fiend rallies, troop development or planned upgrades.
Can I change alliance halfway through? Do not expect points or participation eligibility to transfer. Join your intended alliance before accepting tasks or claiming event rewards.
Key Takeaways
- Accept first, verify progress, then commit the full cost.
- Protect attempts by choosing achievable tasks.
- Compare personal and shared options without assuming identical rules.
- Coordinate real event overlaps and keep growth queues working.