The guide uses the official game client, its event definitions and the release entry preserved in our patch archive. The snapshot’s current season label is Season 2; if a later season replaces it, the historical release notes below still describe what this season introduced.
What changed at the seasonal release
The release note for version 0.8.0 announces the new season alongside new region content, fusions, equipment additions, clan features and redesigned menus. Read it as a description of that release, not as a promise that every later patch leaves those systems untouched. Follow-up fixes can change how an interaction behaves without replacing the season’s name. A guide that gives only the season label is therefore less precise than one that also identifies its client snapshot.
For a returning player, begin with the parts of your normal routine that changed: the destination selector, equipment choices and the record panel. You do not need to master every new system before resuming a familiar run. Pick an objective, check its current requirements and use the relevant tool when a concrete question arises. This makes the update easier to learn than treating a long feature list as a checklist that must be completed immediately.
Seasonal boards and permanent progression are different
The patch archive describes a reset of seasonal leaderboards, clan points, rivalries, missions, streaks and clan records. That is not the same statement as wiping every Pokémon, Lab purchase or account history. Read the specific category named by an update before interpreting a changed rank as lost personal progression. A new board also changes what an impressive position means: its population and accumulated results differ from an older season’s board.
The developer also documented a boundary rule for runs started in the previous season and submitted after the new one opened: those runs remained in history but did not count toward the new season’s boards or clan points. This is why the start and submission context matters when reviewing an apparent discrepancy. Check the official result and leaderboard panel before assuming a save failure. The season label alone does not explain which ranking accepted a run.
Regions added to the route
Storm Coast and Celestial Glacier are named in the seasonal release. Their extracted unlock conditions remain visible in our region explorer, alongside the encounter data supplied by the client. Follow the actual progression chain on your account rather than assuming that a new-season announcement grants immediate entry to every destination. A later fix specifically addressed an earlier-season completion that appeared to unlock the Coast but did not let affected players enter.
The biome catalogue and the season’s region list are separate source fields. An additional stored biome is not automatically another playable destination in the current seasonal route. That distinction is especially important for Lavender Tower, which has a scheduled event context, and for records that are absent from the active-season list. Check availability first, then plan your encounter or unlock objective. The legendary recruitment guide separates finding an associated region from meeting a League challenge.
Move fusions change the shape of a plan
The seasonal release introduces Bill’s Machine and combining maxed moves while freeing a slot. That changes the questions worth asking when preparing a run: which ingredients can your plan obtain, what condition must be met before combining them, and what will you do with the freed space? A powerful-looking final combination is not a complete plan if its route is impractical for your starting choice.
Use the fusion recipe reference for verified extracted recipes and clearly marked gaps. Do not assume that every attractive pair of move names is a valid combination. Subsequent patches repaired fusion behavior and improved the information shown on the machine and move cards, so an old demonstration may not reflect the current interaction. Check the version and the actual client sheet before interpreting a video’s damage or cooldown as a stable promise.
The Lavender Tower schedule is an exact window
The source event is Lavender Tower Night, starting October 21, 2026 and ending November 4, 2026. The panel above preserves the full timestamps, including the UTC time, so the last day is not mistaken for an unrestricted local-calendar day. The schedule describes the published window; a live server may still restrict entry or adjust the event, so use the official event button before committing to a long attempt.
After the scheduled end, this page remains a historical explanation of the event and its source rewards. It does not keep a “live” promotion running simply because a static page was built earlier. You can still inspect the quests and understand an old screenshot, but a surviving description is not evidence that the rewards remain claimable. Follow the official interface for any post-event claim period or later return; we do not invent an extension.
Read a Tower quest before starting the climb
The event data contains 7 quests with explicit objective descriptions and recorded Stardust rewards. Some name a particular encounter or floor; another asks for a restricted approach. The table preserves those descriptions so that a player can choose the intended task before a run. A general goal of climbing higher does not necessarily complete every special condition on the way.
The recorded quest rewards sum to 2,500 Stardust. That is the sum of the listed rewards, not a forecast of what an account will earn in a single session. Completion, eligibility and claiming still matter. Use the achievement and Stardust tracker to keep already-earned rewards separate from future targets, and confirm the actual claim in the official client rather than relying on a local checkbox as proof of payment.
Candles and cosmetic reward descriptions
The event source names its points Candles and lists cosmetic unlock descriptions for the event. Those descriptions can involve collection milestones, achievements or standings. They are different routes to a reward, so do not present every cosmetic as something bought from the same shop. Read the condition attached to the specific item you want and distinguish a personal objective from a competitive placement.
A cosmetic name also does not establish a combat advantage. Treat its documented appearance or title role separately from a build’s numerical effects. The shiny and Wardrobe explanation distinguishes Classic Shiny, mastery looks and other appearance systems. Event cosmetics may share a menu with those systems without sharing their acquisition method. Avoid assuming that earning one look automatically grants every appearance in the same Pokémon line unless the client explicitly says so.
Mode rules and multiplayer access still apply
Lavender Tower has its own event-mode context and does not inherit every Classic setting. The client describes the Tower without difficulty levels, while Classic uses map and difficulty choices. Read the mode reference before transferring a familiar Classic objective into an event run. A shared location name or Pokémon encounter does not establish identical rules for records, progression or rewards.
Co-op is another distinct context. The current client describes team Classic sessions and separate team rankings; it does not justify assuming that any event can be entered as a group. Check the actual official mode picker and room options. Our multiplayer guide explains live access checks, destination restrictions and the difference between a room and a clan. A clan goal or social invitation cannot override a mode that the room does not offer.
Prioritize the things with a real deadline
If the event window is open for your account, read the reward conditions and choose a realistic objective before spending your session on repeat attempts. A clearly understood quest can be a better use of limited time than chasing an unfamiliar leaderboard target. This is planning advice, not a claim that a particular quest is universally easy or that its reward is guaranteed. Your current unlocks, controls and experience affect what is practical.
Permanent learning still has value after the event ends. Understanding the new regions, practicing a fusion route and reading the revised record panels do not become wasted work because a seasonal decoration disappears. Keep deadline-sensitive rewards separate from broader progression goals. When a patch changes an interaction, update the plan from the source note instead of treating the original seasonal announcement as the final rulebook.
Frequently asked questions
When does Lavender Tower Night end?
The extracted event end timestamp is 2026-11-04T17:30:00Z. The panel shows that published window and updates its status as time passes. Check the official game for live access and any announced changes; this wiki does not extend the event.
Did the season reset all personal progression?
The source notes name seasonal boards and clan-related seasonal records. They do not establish a complete reset of all account unlocks or Lab purchases. Read the specific category and check your account’s current state.
Are event reward totals guaranteed earnings?
No. A total adds the rewards listed in the source. You still need to meet the relevant conditions and claim through the official game, and competitive rewards depend on their own standings or eligibility.