Lords Mobile event calendar: why one reminder may not be enough
Use a LordsTools example to distinguish registration, estimated dates and calendar exports. Save the actions you need, rather than only an event's start.
Published · Updated
When planning Lords Mobile events, separate three moments: preparation, registration and the battle itself. An add-to-calendar button may save only one of them. We examined a specific LordsTools example: the page displayed a registration period, while the downloaded file contained one entry for the event itself.
LordsTools is an unofficial community project. Its author explained on Reddit that keeping track of KvK and Guild Fest had been difficult. It is a useful planning starting point; the exact conditions of your round must come from the game.
What the file actually contained
On the screen checked September 26, 2026, the Dragon Arena card showed registration from October 1 at 08:00 to October 2 at 08:00 with UTC+3 selected. Its Apple / .ics file instead contained one entry starting October 2 at 05:00 UTC and ending October 3 at 05:00 UTC. In Moscow, those are 08:00 on the respective dates. The Google Calendar link supplied the same interval.
That file contained no separate registration entry. This describes one particular LordsTools export, rather than confirming IGG's October schedule. We did not import it into a personal calendar; we examined the downloaded file directly.
Open the original screen at full size
After adding an event, inspect the resulting entry in your own calendar. If an earlier action is required, such as registering, agreeing on a team or completing preparation, create a separate reminder. A notification at the event's start cannot replace an action due beforehand.
Precise clock times do not establish a confirmed date
LordsTools uses ≈ for approximate starts and labels some details as unconfirmed. The site explains that it estimates future dates from earlier cycles. A neatly displayed time, complete with minutes, may therefore remain a prediction. Changing the time zone converts the clock time without making the underlying date more reliable.
Choose your time zone first. In the original check, switching from UTC to UTC+3 moved the same card's time by three hours. Then read the status of the event you need. If it appears in the not-yet-tracked section, the calendar lacks data; that does not by itself mean the event was cancelled.
An estimated date can support a reminder to check the next round. Record the time you commit to joining your team after checking the current in-game schedule and the guild's agreement. This keeps uncertainty visible until you make the final decision.
Build a plan you can carry out
Start with two or three events you actually intend to join. LordsTools offers category filtering in its list, while the monthly view helps reveal overlaps. Every row in the shared calendar need not become an obligation. For Homecoming, the next action is to check the absence period and Castle level: event dates alone are insufficient.
For each chosen event, record the next action and its result. Replace prepare for the festival with choose a feasible quest and calculate the time required. The Craft Gear guide, for example, helps check Foundry access and workload before spending speed-ups. For the Diamond battle pass, Premium access, points and reward claims require separate checks.
After an import, compare the entry's date, time zone and purpose with the original card. The registration deadline, overall event window and agreed team deployment time may need separate entries. Use several precise actions rather than one broad reminder to play. Other examples include Lords Puzzle's stages, separate draw and overall duration. In the picture-tile event, earning points and claiming prizes end separately. In Treasure Tiles, check remaining prizes before moving on: you cannot return to the previous level.
