Guild Fest Final Day: Close Out Every Task

On the final day of Guild Fest, the same question starts circulating in guild chat: “Has everyone finished their tasks?” The real problem is often not finding tasks. It is keeping track of who has done what before the event ends. One player has started a task, but their progress is unclear; another says they finished but has not checked their points. Meanwhile, an R4 is trying to tell the difference between war messages.

This guide does not revisit task selection. For that decision, see the Guild Fest task selection guide. The goal here is narrower: close out the work already in progress on the final day. The times below are example checkpoints you can adapt to your guild, not game rules. Always use the in-game event timer for the exact end time.

Split the final day into three checkpoints

With about 24 hours left, run the first check-in: Who has finished, who is midway through a task, and who has not replied? The aim is not to assign everyone more work; it is to identify what might remain unfinished. In a 20-player guild, for example, if four players have not reported their status, their tasks are uncertain too. “Finished players, confirm; anyone still working, send an estimated finish time” is more useful than a general reminder.

Check again with about 12 hours left. Reassess tasks that are likely to take too long, and ask when each player will be online. The final check, with about two hours left, is for closing open tasks—not inventing a new plan. If a task is still incomplete, establish how far along it is and whether it can finish before the timer runs out.

Set phone alarms for each checkpoint, not just the event's end. Reopen the in-game timer when setting them so your time zone or daily routine does not mislead you. LordsRally's optional LM Events cards can send official event information to your group; this notification type is off by default. You can review the tool's scope on the features and commands pages. Even if you use notifications, confirm Guild Fest's exact end time in the game.

Put every task status in one table

The most useful final-day document is not a complicated points spreadsheet. It is a simple four-column list: player, task status, estimated finish, last confirmation. Mark status as “finished,” “in progress,” or “awaiting reply.” Do not count “I'll do it” as a finished task. Ask players who report “finished” to confirm their points on the in-game screen.

Suppose 11 of 18 players have finished, four are still working, and three have not replied. Rather than sending the same message to all seven, split the follow-up: Ask the four working players for finish estimates, and ask the other three whether they will participate. That way, the R4 does not treat someone actively working on a task the same as someone who has not logged in.

Share the table somewhere easy to find in guild chat, but do not start a long message chain for every small update. Send one current summary at each checkpoint, such as: “Finished: 11; in progress: 4; awaiting reply: 3.” If those numbers have not changed by the next check-in, communication may be part of the problem. Establish who cannot be reached, then focus on the remaining work that can be done.

Filter tasks by the time left

On the final day, time to completion matters as much as a task's points. If a player is planning a two-hour gathering march with only 45 minutes left, do not present it as a last-minute solution. Likewise, telling someone to “finish it” will not help if they lack the resources or speed-ups their research needs. Ask what is missing and when they could realistically finish.

Use this order: First, identify tasks already underway that can be completed. Then check the required resources and when the player will be online. Only after that should you decide whether anyone should start something new. If a player will log in 30 minutes from now and the event ends in an hour, they have far less time to finish than the timer suggests. Plan from the moment they return to the game.

It can be tempting to advance two events with one action, but do not put a Guild Fest task at risk on the final day just to wait for another event. For more timing examples, see the Guild Fest and Hell Event guide. Here, the priority is finishing work already started within the current timer.

Give R4/R5 communication clear owners

On closing day, having everyone message everyone may seem fast, but replies get lost. Have one R4 collect task statuses and another speak with players who are online. The R5 can watch the guild's overall shortfall and make final decisions. Three officers separately asking the same player “Done yet?” will not speed up the answer.

For example, if three of your 12 active players are trying to finish tasks, assign one contact to each. Make the question specific: “What remains on your task, when will you be back online, and can you confirm completion before the event ends?” A call for “everyone to finish their last tasks” does not show you who needs help.

Set a clear limit for following up with offline players, too. If they do not answer the first check-in, ask again at the next checkpoint; do not spend all the remaining time waiting for a reply. This is not about blaming anyone. It is about planning around confirmed participation. As the deadline approaches, use short status messages in a consistent format so task updates do not disappear among war calls.

Finish the closeout on the rewards screen

Run the final check before the event timer reaches zero. Ask each player to compare their “I'm done” message with their task and points status in the game. If the open tasks in your guild summary do not match players' latest confirmations, you know whom to contact. For example, if the table still shows two tasks “in progress” but both players say they finished, verify the result on the event screen rather than relying on chat messages alone.

Then check reward requirements in the game. Do not rely on an old screenshot to decide which rewards are available or what action is needed; open the current event screen. After the event closes, leave a short handover note: How many players could not be reached? Which tasks ran out of time? When should the first check-in happen at the next Guild Fest? Those three lines become the starting plan for the next final day.

If finishing a task reveals a resource shortfall for research or gathering, first calculate what you have and what you can actually finish. If you still need resources, ready-made resource packs are available on our site: RSS resource packs. Buying resources alone does not mean a task will finish in time. You can find more event plans on the blog.

Set up your guild's final-day check-ins today. If you want to add event notifications to your group, contact LordsRally.