Last Asylum: Plague Hunt Battle Strategy Guide for Alliance Leaders

For Last Asylum: Plague R5s and R4s who want the most out of Hunt Battle, Wandering Blight and Thief Hunt through preparation instead of scrambling.

Hunt Battle is the main alliance-wide combat event in Last Asylum: Plague. Two alliances compete to clear 15 waves of Blights in their territory for scaling rewards. Alliance Duel scores individual actions across a week. Hunt Battle scores combined combat output inside one timed session.

For top alliances, this is where each member's troop investment turns into alliance-wide rewards at the biggest scale the game offers. It rewards preparation and timing. Alliances that know the wave structure, the difficulty choice and march discipline before the start get far more out of it than alliances that react in real time.

This guide covers how Hunt Battle works, Thief Hunt and Wandering Blight, choosing difficulty, wave-by-wave coordination, and the checklist that separates steady full clears from frustrating partial ones.

How Hunt Battle works

Difficulty: when the alliance starts Hunt Battle, it picks one difficulty that stays locked for the whole challenge. It sets Blight wave strength and the reward tier.

Preparation phase: the first 5 minutes after the start are setup. Blight spawn points appear in alliance territory, but no Blights spawn yet. Use this window to position and coordinate, not to wait.

Combat phase: after prep, 15 waves of Blights spawn, each harder than the last. Total Blights killed within the time limit decides how many rewards you get. More kills, more rewards.

Marches: troops attacking event Blights have a fixed 15-second march and return time for every member, wherever they are on the map. Distance does not matter. Everyone sends marches from where they are.

Quick reference

• 20+ alliance members needed, R5 or R4 starts it, one attempt per event period
• 5-minute prep phase, then 15 waves of rising difficulty
• Fixed 15-second send and return for all members, wherever they are
• Total Blights killed decides rewards, not just wave completion
• Difficulty is locked at the start and cannot change mid-event

Choosing difficulty: the most important decision

You pick difficulty before the event and it holds for all 15 waves. Too low and you leave higher-tier rewards on the table. Too high and the alliance stalls mid-event and gets fewer rewards than a lower difficulty would have given.

Rewards scale with total Blight kills, not only wave completion. A full clear at difficulty 3 gives more than a partial clear at difficulty 5. The right difficulty is the highest one where your alliance reliably clears all 15 waves in time.

How to judge your ceiling before you start

Active members in the event window matter more than roster size. If 20 members start but only 15 are online for combat, your firepower drops by 25%. Confirm real attendance before you pick, not expected attendance.

Average troop tier decides whether late waves become a wall. If most of your active roster is T8 or above, go higher. If half the roster is still T5 to T6, go lower. The weakest members decide whether waves 11 to 15 clear.

Hero investment sets damage per march. Members with fully built UR heroes do far more per march than members with scattered heroes at the same troop tier. Count hero development next to troop tier.

Start one difficulty below what you think your ceiling is for the first cycle. First guesses almost always overrate what the alliance can do in high-pressure waves. A safe first run that full-clears beats an ambitious one that stalls at wave 12.

When to push difficulty higher

Push higher only if both are true: your active member count held through all 15 waves last cycle, and the final waves cleared with time to spare. If you finished wave 15 with less than two minutes left, you are already at your ceiling. With five or more minutes left, one step up is likely safe. Never jump two difficulty tiers after a single clean clear.

Wave-by-wave strategy

Waves 1 to 5: set the tempo

The first five waves should clear fast at any sensible difficulty. They test participation, not power. The goal is nonstop marching from the first second of combat.

Every online member sends marches right away. The fixed 15-second cycle means fast redeploys are possible and expected. Members who wait for one Blight to die before targeting the next break the tempo you need for the mid waves.

Waves 6 to 10: steady pressure and focus fire

Mid waves raise Blight HP and damage a lot. Uncoordinated alliances slow down here. The fix is focus fire: everyone hits the same Blight until it drops, then moves together to the next one.

Wave commanders call targets in alliance chat or your outside coordination channel. With a 15-second cycle, even short calls raise the kill rate. Members with the strongest troop tiers and biggest squad loads should lead target switches. Their marches hit hardest, so getting them onto the right Blight first beats waiting for everyone to line up.

Waves 11 to 15: all-in sprint

The last waves have the highest Blight HP and the most time pressure. This is where your prep pays off.

Use any alliance-wide combat buffs before wave 11 opens, not in a panic at wave 14. Buffs used in the final waves affect far more kills than buffs saved for a wave that stalls.

Members march at the maximum rate the 15-second cycle allows. No idle time. Leaders watching the event call out inactive members and shift focus to cover them. Every second a march sits idle is a Blight that lives longer.

Using the 5-minute prep window

The prep phase is the most important coordination window of the event. Use all of it.

• Confirm the active headcount. Count who is online and ready. If it is much lower than expected, rethink difficulty before it locks.
• Assign wave commanders. Pick two or three of your most experienced members to call targets. They track Blight HP, spot near-dead targets and redirect firepower without confusion. One clear voice in the late waves beats five giving mixed orders.
• Check Blight spawn points. They appear during prep. Knowing where Blights will show up saves march cycles you would lose chasing targets across the territory.
• Remind members about the fixed march time. Some think being far from alliance territory makes them less useful. It does not. Everyone gets the same 15-second cycle. Nobody should sit out because they think they are too far away.

Wandering Blight and Thief Hunt

Wandering Blight

Wandering Blight is a separate world map event. High-difficulty Blight bosses spawn at set locations across the warzone. Unlike Hunt Battle, which runs in alliance territory with a fixed march time, you have to march to the boss on the world map, and alliance rallies are the main way to fight it. It drops rare materials, including gear components and hero shards you cannot reliably get elsewhere.

Assign rally leads before the spawn windows and keep your top-power members on standby. Alliances that do this beat alliances that react after the spawn.

Thief Hunt

Thief Hunt is a time-limited chase. A Thief appears on the map carrying stolen alliance resources, and members must find and defeat it before the timer runs out. Speed is everything: the faster the alliance gets enough troop power to the Thief, the more resources it recovers. An R4 announcing the Thief's location the moment it spawns is the single most important action.

R4 coordination across these events

Hunt Battle, Wandering Blight and Thief Hunt all need an R4 or R5 to start them. Either rank can start Hunt Battle. What matters is who is reliably online at the confirmed start time. For alliances running several events a week, the alliance guide covers how officer titles should follow who is actually online in each event window.

The God of War R4 title is the natural owner of Hunt Battle. The God of War runs combat coordination: starting Hunt Battle at the confirmed time, calling difficulty, assigning wave commanders and watching the combat phase. If your R5 is not always around in the event window, give this job to a specific R4 who is. A God of War who is offline during Hunt Battle means the event misses its window.

Alliance leader checklist

• One week before: survey the active roster, count confirmed participants for the event window, check average troop tiers and hero investment, and pick difficulty from that data.
• 24 hours before: announce the exact start time in alliance chat and your outside channels. Confirm an R5 or R4 can start it. Remind members that distance does not affect participation.
• During prep (5 minutes): confirm headcount, assign wave commanders, check spawn points, and remind members about the 15-second cycle and nonstop marching.
• During combat: commanders call targets, focus fire one Blight at a time in mid and late waves, use alliance buffs before wave 11, and watch for inactive members.
• After the event: review total kills, waves cleared and time left. Decide whether the difficulty was right and adjust next cycle based on real results, not guesses.

Hunt Battle rewards the whole alliance's investment. Every member's troops and heroes feed the result, so stronger troop tiers and better hero builds across the roster mean more kill capacity on the day.

Where Packsify fits

Packsify buys the Last Asylum packs you pick through the official Apple App Store or Google Play. With Packsify you get up to 13% more pack value for the same money. New to Packsify? Start with the Last Asylum top up guide and how we keep accounts safe.

Last Asylum also runs an official top-up center on the web (globallap.com). It gives +5% Banknotes on every pack bought there, a 30-day avatar frame with +2% research speed for any top-up, and web-only packs. For those web packs it can be the better deal, and if you use it, that is fine. Packsify is for players who want the exact App Store or Google Play pack bought for them.

See Last Asylum packs and prices

Spotted a mistake? Tell us in the Play Smarter Discord and we will fix it.

Packsify is an independent service, not affiliated with Last Asylum: Plague or its publisher.