Whiteout Survival Crazy Joe Reinforcement and HQ Defence Plan

Crazy Joe works best when an alliance treats it as a shared defence operation. Agree who protects each city, which marches move to headquarters, and who needs help after a failed defence. Sending every available march without a plan can leave one member overloaded with support and another exposed.

The first objective is to keep useful defence opportunities alive. The second is to place reinforcements where they can contribute. A personal score matters, but the reward milestones also require alliance progress.

The rules your plan must account for

You can participate after reaching Furnace Level 7 and joining an alliance. Crazy Joe stops attacking your city after two failed defences. That cutoff is why an early failure should trigger a support decision rather than a shrug.

The event has up to 20 waves. Waves 10 and 20 target Alliance HQ, while waves 7, 14 and 17 target only some members. Shields do not block Crazy Joe; a defeat does not take your resources. You can reinforce allies to earn points even when the plan is not centred on defending your own city.

For reward milestones, both the personal and alliance point requirements must be met. A large personal score alone does not unlock a chest whose alliance requirement remains unfinished. The alliance also needs a built HQ to launch the event, and R4/R5 officers can schedule or activate it and choose the HQ.

Prepare a roster rather than a chat full of requests

Before the start, assign a coordinator and a backup. Their job is not to micromanage every troop. It is to make sure that the same few strong players are not being asked to solve three problems at once.

A small planning table is enough:

These are example assignments, not required troop counts. Scale the table to the alliance. Include people who will be offline, but do not give them a job that requires a precise recall and redeployment unless someone has arranged a workable alternative.

For each support arrangement, establish three facts:

1. Who is defending whose city at the start?
2. Which of those marches may leave for another target?
3. Who announces that a defence has failed or that coverage is missing?

Reciprocal support is useful because responsibilities are clear. It need not mean identical troop numbers or identical account strength. A smaller player can still be a reliable partner if the assignment suits the troops and march slots they actually have.

Separate city coverage from the mobile group

Give some marches a stable city-defence assignment and identify others that can be redirected. If everybody is treated as mobile, the alliance can accidentally abandon the same vulnerable cities at the same time.

The mobile group has two main jobs: respond to a developing weakness and prepare for HQ defence. A member with several available marches may cover both jobs, but the coordinator should know which march is committed where.

Use short status messages that describe an action:

• “City support arrived.”
• “One defence failed; support needed.”
• “HQ march available.”
• “Returning to assigned city.”

Avoid messages such as “Help!” with no target, or “Everyone recall!” when only the HQ group needs to move. Clear target names or shared coordinates reduce the chance of sending useful troops to the wrong place.

Use the wave changes as decision points

The numbered wave changes follow the wiki’s Crazy Joe rules; the allocation plan is a practical way to respond to them.

Do not treat a wave number as an instruction to pull troops out of an unfinished defence. Confirm that the march you want to move has finished its current job. A perfect HQ lineup that arrives late is not the same thing as a defence that was ready when needed.

Plan the HQ transfer before the event

The difficult part of HQ defence is often coordination, not picking another hero. Name the HQ group in advance and give it an unambiguous destination. If the alliance has more than one headquarters, “Go to HQ” is an incomplete instruction.

Work backwards from arrival:

• The march must reach the selected HQ before the attack.
• Before travelling there, it may need to return from its city assignment.
• If it leaves a city that still needs support afterward, someone must know how that coverage will be restored.

A worked HQ timing decision

Suppose an assigned march needs 25 seconds to return from its current location and another 40 seconds to reach HQ. Allow a 15-second margin for issuing orders and small delays. These are hypothetical travel times, not Crazy Joe’s fixed wave timing.

The decision rule is: time remaining must cover return travel plus outbound travel plus your margin. With only 60 seconds left, this march cannot satisfy the example plan. Use an already-mobile reserve with a shorter route instead of ordering an impossible transfer. If the original march is still needed in an unfinished city defence, leave it doing that job and call the backup.

Use the actual travel times of your assigned marches. The margin is a planning choice, not a game mechanic; choose one that suits how quickly your group can react.

For the first HQ defence, prepare the next destination as well. The transition is not complete just because HQ survived: a march that remains idle or stays in the wrong place can leave its city partner without the support the plan assumed.

For the final HQ defence, use the force the alliance has agreed to commit. Avoid a last-second competition to replace everyone else’s contribution merely to chase personal points.

Respond differently after one failure and two

After one failed defence, ask whether the next defence can be improved. Identify a missing reinforcement, a march that left early or an assignment that was too weak. Moving an available support march can be more useful than spreading another small contribution across an already secure city.

After the second failure, change the assignment. The developer’s help article states that attacks stop at that point. Troops waiting for another attack on that city no longer have the same job. Coordinate their next destination instead of leaving them there by habit.

Do not confuse losing your own city’s remaining attacks with having nothing left to contribute. Look for a remaining ally defence or an upcoming HQ assignment. Keep the coordinator informed so that the reinforcement roster reflects what is happening now, not what was agreed before the first wave.

Do not turn scoring advice into an unconditional rule

A coordinated troop exchange must answer both sides: where your troops go and who defends your city. Do not empty a city merely because a copied scoring instruction says to; first establish that the expected support can arrive and hold.

Likewise, exact troop ratios and absolute “never heal” instructions are not substitutes for an alliance plan. Prioritize a reliable defence and milestone progress before optimizing how points are distributed. Follow the composition assigned for your difficulty and available troops, then review the result. A tactic that helps share points in an already-safe defence is not automatically useful when cities are failing.

Diagnose the result without blaming the smallest accounts

After the event, separate three questions:

A failed plan is not automatically proof that every member needs more power. If reinforcements were late or sent to the wrong place, fix that first. Conversely, if the assignments were correct and the defences still could not hold, do not disguise a strength problem as a communication problem.

A reusable alliance briefing

Copy and fill in this message before the event:

“Crazy Joe starts at [time and time zone]. Selected HQ: [name or shared coordinates]. Coordinator: [name]; backup: [name]. Follow the city-support assignments. HQ group: [names]. Report one failed defence immediately. After two failures, tell the coordinator so support can move to another target. Only the assigned HQ group recalls on the HQ call. After the first HQ defence, return to your city assignment. Do not change shared coverage without telling your partner.”

The best improvement is usually a specific one: a covered city, an on-time HQ march, or a reinforcement moved away from a target that will no longer be attacked. Make those decisions predictable, and the alliance can spend less of the event repairing avoidable gaps.