Event Timers: A Guild Plan to Avoid Missed Starts

Preparing for an event only to miss it because you read the time wrong is almost as frustrating as sending the wrong troops. In a guild with players from different countries, “We start at 21:00” is not enough: 21:00 in whose time zone? Does the event open then, or end then?

Rather than building a week-long calendar, this guide focuses on announcing and acting on the time of one event accurately. The same method works for Guild Fest, KvK, Dragon Arena, or a Wonder battle. For broader planning, see the seven-day guild calendar guide.

Read the event card before announcing a time

Don't write an announcement based on the large number in a screenshot. First, read what the countdown is counting toward. Time until an event opens, time until it ends, and a task's own time limit call for different decisions. Open the card's description and objectives; don't assume how participation or points work.

For example, if your local time is 19:30 and the card says “1 hour 15 minutes remaining,” note the end time as 20:45. That does not mean you should start your action at 20:45. Set a final guild check for, say, 20:15, leaving time to spot an unfinished task and change plans. If the same countdown were showing time until the start, 20:45 would be the opening time instead.

• Event name: Which card should players open?
• Countdown meaning: Time until the start, the end, or the task's own deadline?
• Required action: Enter the event, make a point-scoring move, or complete a task?

Local time, UTC, and countdown: the three-way check

Choose one standard for guild announcements. If your team is in Türkiye, Türkiye time is straightforward; for an international team, adding UTC helps prevent confusion. Türkiye time is UTC+3. Don't calculate a teammate's local time from memory, especially around daylight saving changes—ask them to verify their own conversion.

Suppose an R4 notes October 28 at 18:00 UTC for an event. In Türkiye, that is 21:00 on the same day. But October 28 at 21:00 UTC is 00:00 on October 29 in Türkiye. A three-hour difference may seem small, but crossing midnight can put the wrong date in your announcement and disrupt the entire check-in.

After converting the time, return to the game and read the countdown again. If it's 20:00 in Türkiye and you believe the announced opening is one hour away, the card should show roughly one hour remaining. If it doesn't, pause before posting: you may have mixed up the time zone, date, or start and end times.

Give the guild one clear line: “Event: Dragon Arena | Announced time: 21:00 Türkiye / 18:00 UTC | First check-in: 20:30 Türkiye | Source: in-game event card.” These times are only an example template; take your event's actual time from its card.

One-line guild announcement and attendance check

The correct time alone won't secure attendance. Your announcement should also say when you'll know who's ready. For KvK, the fighting roster and support players have different roles; Dragon Arena needs members who can enter; a Wonder battle needs a rally leader and fillers. Ask for a role, not just “I'll be there.”

Try this guild routine: 60 minutes before opening, an R4 or R5 checks the card again and confirms the time; 30 minutes before, close the attendance and role check; 10 minutes before, call backups for missing roles. These are team checkpoints, not mandatory game timers. Move them earlier if your plan involves long marches or extra preparation.

Three attendance replies are enough: “ready,” “running late,” and “can't attend.” Someone missing the last rally fill is a different problem from someone who will miss the event entirely. If an R4 knows early, they can reassign the role; if they find out at opening, everyone waits.

Choosing the right Dragon Arena time slot is a separate decision; use the Dragon Arena time-slot guide for that. This check-in confirms who can actually attend the slot you've chosen.

Set task deadlines against the event deadline

In Guild Fest and Hell Event, timing mistakes usually affect the final move, not the opening. Read the task requirements and its own time limit, then note the event's end time separately. If there are two deadlines, plan around the earlier one. Don't spend research, construction, or training speed-ups before checking what actually awards points.

Suppose the card has 45 minutes left and you're waiting for a guildmate to transfer resources for your move. Instead of assuming you'll finish at the last minute, set a decision point with 20 minutes remaining: if the resources haven't arrived, switch to a move you can complete or save the spending for another suitable event. After acting, check that the points or task progress appear on-screen. That verification buffer matters when connections or coordination falter.

Calculate your resource needs before that decision point. Count your available stock and resources in your bag first. If there's a shortfall, ready-made RSS resource packs are available on our site. But even if the resources arrive, don't finish a move just because there's room in the schedule when it doesn't meet the event conditions.

For a more detailed decision process on when to finish a Guild Fest or Hell Event move, see the task deadline guide.

Final checks and handoff on event day

An R4's job on event day isn't to repeat the same time. It's to identify what has changed. In the final check before opening, ask three questions: Does the in-game countdown match the announcement? Are the critical roles filled? Does everyone know their next action? In a Wonder battle, “we're ready” isn't enough—name the rally leader and who will coordinate the first fill.

A handoff message might read: “10 minutes until opening; countdown checked. R5 will make the first call, with an R4 ready as backup. Tell us now if you can't attend.” If someone else takes over after the event starts, they shouldn't simply reply “I've got it” to the old announcement. They should pass along the current countdown and the next decision, so two officers don't issue calls based on different times.

If you use an external reminder, don't treat it as a replacement for the in-game card. In LordsRally, LM Events notifications are off by default; when enabled, they send official in-game event cards to the group in the selected language. On a Wonder battle day, !wow timers can also help. Treat these as secondary checks; you'll find the tools on the features and commands pages. For other event preparations, browse the blog guides.

If event times keep getting mixed up in your guild, try this template for the next one. Contact us if you'd like to add event notifications to your team's workflow.