Skip to content

Executioner's Fall

When: every 2 days. The window lasts 2 days; an R5 or R4 picks the start time inside it. What it is: an alliance burst-damage event against a Goblin Machine that spawns near your hive. Why it matters: a strong recurring source of energy cores and materials, and one of the few events you can contribute to while offline.

The short version

  1. An R5 or R4 sets the start time. Coordinate it for when your alliance is actually awake.
  2. A 30 minute countdown begins, then the Goblin Machine spawns near your hive.
  3. Anyone can start a rally — you do not need to be an officer.
  4. Rallies cost no stamina. There is no reason to hold back.
  5. Watch the clock: a 4 minute march with 3 minutes left will not land.
  6. Enable offline participation up to 12 hours in advance if you will be away.
  7. Both personal and total alliance damage drive rewards, so everyone's hits count twice.

Setting it up

The event window runs 2 days and recurs every 2 days, so it is close to continuous. Within that window an R5 or R4 sets the start time.

That choice is the single biggest lever on your alliance's result. Pick a time when most of your members are online — a technically optimal slot at 04:00 server time scores less than a mediocre one at peak activity.

Once started, a 30 minute countdown runs and then the Goblin Machine spawns. You cannot choose where — it appears on the map near your alliance hive.

Your Goblin Machine is visible only to your own alliance, so there is no risk of another alliance interfering or stealing the kill.

Fighting it

It is rally-only. You cannot attack it directly.

Anyone can start a rally, not just officers. This is unusual and worth telling your members explicitly, because many assume rallies are an officer function and sit waiting for someone else to open one.

Rallies cost no stamina. There is no budget to manage and no reason to conserve. Fill every rally slot you can.

The clock is the whole tactical problem

The fight is short, and marches take real time. A 4 minute march with 3 minutes left on the clock will not land — you have spent the queue for nothing.

So:

  • Early in the window, start rallies freely and let people join from anywhere.
  • Late in the window, only players close to the machine should be starting or joining. Check your march time against the remaining clock before you commit.
  • Alliance leaders: call the cutoff in chat. "Stop joining unless you're under 2 minutes out" is worth more than any amount of damage advice.

Offline participation

You can enable offline participation up to 12 hours in advance, and your queues will auto-rally without you.

This is the feature that makes the event work for a spread-out alliance. If the start time lands while you are asleep or at work, set it the night before and you still contribute. Tell new members about it — it is easy to miss and it is the difference between a member scoring and scoring zero.

Rewards

Both personal damage and total alliance damage drive rewards. Your hits pay you directly and push the alliance total that pays everyone.

The practical implication: there is no free-riding and no point saving yourself. An alliance where everyone throws every queue in scores better per person than one where half the members wait to see if it is worth it.

Executioner's Fall is repeatedly cited as a strong source of energy cores, which are the gate on red gear — see Hero Gear. Given it runs every two days, it is arguably a larger lifetime source than any single rotating event.


For alliance leaders

Set the time for your members, not for the calendar. Peak activity beats everything else.

Announce the start time in advance so people can enable offline participation.

Say out loud that anyone can rally. Members routinely wait for an officer who is not online.

Call the march-time cutoff near the end.

Common mistakes

Waiting for an officer to open a rally. Anyone can.

Holding queues back to save stamina. Rallies here cost none.

Joining a rally that cannot land in time. Check march time against the clock.

Not setting offline participation before a bad-timezone start. Twelve hours of notice, and most people never use it.