Home / Wuthering Waves Guides / WuWa Version History: 22 Patches, and the 3.9 Date

Every WuWa patch date since 1.1, the window each one used, what it paid and how big the download was, plus where 3.9 lands.

Updated 2026-11-16

Home / Wuthering Waves / Guides / Version history

WuWa Version History: 22 Patches, and the 3.9 Date

Wuthering Waves has run 22 version updates between 1.1 and 3.8, and the last several have landed on a tight six-week rhythm. The next one is the only part people look up before it is announced, so this page keeps two things side by side: what every maintenance notice has actually printed, and what that record says about 3.9.

Short version: the notices point at December 22, 2026 for 3.9, because 3.8's own event slate and a cycle timer in its patch notes both stop at that date. The long-run median gap between versions is 42 days, which would put the patch on Dec 24, 2026 instead. Both dates are in the same week, and the gap between them is the honest size of the uncertainty.

What the 3.9 date rests on

Three things point at a date, and they do not carry the same weight. Kuro has not announced 3.9 yet, so none of this is a confirmation. What follows is the gap between an inference and a notice.

SignalWhat it saysHow strong it is
Cycle timer in the 3.8 patch notesSecond Endstate Matrix Cycle ends at 03:59 on December 22The strongest. A 03:59 end is one minute before a 04:00 maintenance, and that is the shape every version start on this page takes
3.8 event windowsUnwritten Dreams closes at 11:59 on December 21, the day beforeStrong. In 3.7 the last leisure event closed sixteen hours before the 3.8 patch began
Six-week rhythm42 days after November 12 lands on Dec 24, 2026Weaker on its own, because the same record ranges from 32 to 49 days

December 22 is a Tuesday. That is worth flagging because 16 of the 22 patch days on record are Thursdays. Kuro has patched on a Tuesday once before, at 2.3 in April 2025, so a Tuesday is not a contradiction. It just means the event and cycle timers have to carry the argument rather than the weekday habit.

All 22 version dates in one table

Every row comes from the maintenance notice Kuro published for that version, not from a wiki timeline. The gap column is the number of days since the previous version went live, and it is the raw material for everything below.

VersionLive (UTC+8)DayGapWindow
1.1Jun 28, 2024Fri—06:00–13:00
1.2Aug 15, 2024Thu4806:00–13:00
1.3Sep 29, 2024Sun4504:00–11:00
1.4Nov 14, 2024Thu4604:00–11:00
2.0Jan 2, 2025Thu4904:00–11:00
2.1Feb 13, 2025Thu4204:00–11:00
2.2Mar 27, 2025Thu4204:00–11:00
2.3Apr 29, 2025Tue3304:00–11:00
2.4Jun 12, 2025Thu4404:00–11:00
2.5Jul 24, 2025Thu4204:00–11:00
2.6Aug 28, 2025Thu3504:00–11:00
2.7Oct 9, 2025Thu4204:00–11:00
2.8Nov 20, 2025Thu4204:00–11:00
3.0Dec 25, 2025Thu3504:00–11:00
3.1Feb 5, 2026Thu4204:00–11:00
3.2Mar 19, 2026Thu4204:00–11:00
3.3Apr 30, 2026Thu4204:00–11:00
3.4Jun 8, 2026Mon3904:00–11:00
3.5Jul 10, 2026Fri3204:00–11:00
3.6Aug 20, 2026Thu4104:00–11:00
3.7Sep 30, 2026Wed4104:00–11:00
3.8Nov 12, 2026Thu4304:00–11:00

Two things fall out of the table before any interpretation. The first is that the windows barely move: 20 of 22 are 04:00 to 11:00. The second is that the early version numbering does not line up with calendar years the way people assume. Version 1.1 landed in June 2024, and 2.0 did not arrive until January 2025, which is why the largest gap on the page sits between 1.4 and 2.0 rather than anywhere in the current run.

Why the dates look so regular now

The median gap is 42 days across all 21 intervals, and 42 days is exactly six weeks. That is the mechanical reason Thursday survives: a six-week step keeps the weekday, so a Thursday patch schedules the next Thursday patch. The mode is not the whole story though. Of the 21 gaps, 8 are exactly 42 days, and the rest are scattered between 32 and 49.

The short gaps are the interesting ones. Four versions arrived 35 days or less after the one before: 2.3 at 33, 2.6 at 35, 3.0 at 35 and 3.5 at 32. Those are the patches that arrived early enough to break the weekday pattern, and they are also why a 40-day estimate for 3.9 is plausible rather than wishful.

The long gaps sit in a different era. The 49-day gap into 2.0 came with a region launch and a new platform build, and the four gaps above 44 days all fall before the six-week rhythm settled. Nothing in the 2026 record approaches them: the largest of the last nine gaps is 43 days.

The window moved once, in 2024

The 04:00 to 11:00 maintenance is not a rule anyone wrote down. It is a habit that started with 1.3. Versions 1.1 and 1.2 ran 06:00 to 13:00, two hours later, and both of those were also seven hours long. Every notice since has used the earlier slot, which makes the 04:00 start the safest single assumption on this page and the 06:00 pair the exception worth remembering.

Version 1.3 also owns the only weekend patch in the record. It went live on Sunday, September 29, 2024, four days after its notice went out. Nothing about that date looks deliberate in hindsight, but it is the reason a claim like "patches always land on a weekday" would be wrong by one.

16 Thursdays out of 22

The weekday split is lopsided enough to be useful as a soft filter when you are guessing a date.

DayVersionsWhich ones
Thu161.2, 1.4, 2.0, 2.1, 2.2, 2.4, 2.5, 2.6, 2.7, 2.8, 3.0, 3.1, 3.2, 3.3, 3.6, 3.8
Fri21.1, 3.5
Wed13.7
Tue12.3
Mon13.4
Sun11.3

The non-Thursday patches are 1.1 and 2.5 on a Friday, 1.3 on Sunday, 2.3 on Tuesday, 3.4 on Monday and 3.7 on Wednesday. Four of those six arrived in the last two years, which is a reminder that the Thursday habit is a tendency rather than a schedule. If you are planning time off around a patch, the maintenance window matters more than the weekday: seven hours, starting at 04:00 server time, every time since 1.3.

The same compensation line, 22 times

Every one of the 22 notices carries the identical compensation sentence: Astrite x300 and Crystal Solvent x2. Not a variant, not a scaled amount, the same two items in every notice since June 2024. The eligibility clause has also stayed fixed, down to its phrasing: create a character and unlock the Mail feature before the maintenance begins, or the mail does not arrive.

One piece of wording did change, and it matters when you read an old notice. The claim deadline used to read "before the Version 1.2 update" and now reads "until the next version update", which is the same rule said in a way that survives renumbering. The patch notes also repeat the whole block, so a version with a separate bug-fix Astrite line pays the maintenance amount twice over: 3.7 and 3.8 both do it.

How much warning you get

The maintenance notice is not the first signal, but it is the first one with hours in it. Lead time between the notice and the patch ranges from 3 to 10 days, with a median of 6. If 3.9 lands on December 22, the notice that confirms it should be published around December 18 to 19.

The order of announcements has been stable for a year. A version preview goes up with the schedule, the maintenance notice follows with the exact window, and the update content post lands a day or two before the patch. The pre-download opens ahead of all of it: 17 of the 22 notices state a pre-download start, and from 2.3 onward it has opened at 10:00 two days before the 04:00 maintenance, which is 42 hours of warning. The three earliest ones used 09:30 and bought themselves an extra hour.

What each patch asks you to free up

Storage numbers appear in two different places and are easy to mix up. The pre-download block states what the download needs and what it actually weighs. The system requirements block states the total footprint the game expects on the device. Three notices print the first set, all of them from 3.6 onward, so the footprint series is the one with a usable history.

VersionLiveAndroid/iOSMacPC
2.2Mar 27, 202528 GB60 GB60 GB
2.3Apr 29, 202528 GB60 GB60 GB
2.4Jun 12, 202531 GB60 GB60 GB
2.5Jul 24, 202531 GB70 GB70 GB
2.6Aug 28, 202531 GB80 GB80 GB
2.7Oct 9, 202535 GB80 GB80 GB
2.8Nov 20, 202535 GB85 GB85 GB
3.0Dec 25, 202570 GB150 GB150 GB
3.1Feb 5, 202670 GB150 GB150 GB
3.2Mar 19, 202660 GB130 GB130 GB
3.3Apr 30, 202645 GB130 GB130 GB
3.4Jun 8, 202650 GB135 GB135 GB
3.5Jul 10, 202660 GB155 GB115 GB
3.6Aug 20, 202665 GB160 GB110 GB
3.7Sep 30, 202660 GB150 GB100 GB
3.8Nov 12, 202660 GB155 GB100 GB

The series is not a growth curve. Mobile goes from 28 GB at 2.2 to 70 GB at 3.0, back down to 45 at 3.3, then up to 65 at 3.6 and back to 60 at the current version. Mac peaked at 160 in 3.6 and sits at 155 now. These are the notices' recommended free space, which tracks the patch being installed and the platform build, not the size of the whole game.

Where the pre-download numbers do exist, they tell a sharper story. The PC reservation halved between 3.7 and 3.8, from 46 GB down to 15, while the actual package went from 26 GB to 13. That is the split announcement the 3.8 pre-download guide covers in detail, and it is the largest drop between consecutive versions in the archive.

VersionPre-download opensPC reserve / actualMobile reserve / actual
3.62026-08-1850 GB / 22 GB33 GB / 13 GB
3.72026-09-2846 GB / 26 GB20 GB / 13 GB
3.82026-11-1015 GB / 13 GB13 GB / 9 GB

What the notices do not cover

The gaps are consistent enough to list. Console maintenance times never appear in the PC and mobile notices, so a PlayStation player reading this page should not assume the 04:00 start applies to them. Package sizes only show up from 3.6, and total footprints only from 2.2. Nothing in the archive explains why a version runs long or short. And there is no official page that publishes the next patch date in advance, which is the reason the first section of this article has to lean on event timers at all.

FAQ

When is the 3.9 release date? December 22, 2026 is what the 3.8 timers point at, with December 24 the date the 42-day median would give. Kuro has not published the maintenance notice yet.

How long is a WuWa patch? The median gap between versions is 42 days, and the full range is 32 to 49. The recent run sits between 32 and 43.

What time does maintenance start? Maintenance starts at 04:00 UTC+8 and runs seven hours, ending at 11:00. That has held for every version since 1.3; 1.1 and 1.2 ran 06:00 to 13:00.

How much Astrite does a patch pay? Astrite 300 from maintenance compensation plus Crystal Solvent x2, in all 22 notices on record. 3.8 added a separate 300 for bug fixes, which is an exception rather than a new baseline.

Does pre-download cost anything? No. It opens two days before the patch at 10:00 server time and lets the client fetch the package early. You still cannot log in until maintenance ends.

Where are the banner dates? They move on a separate cycle inside each version. The banner history has every window, and the 3.8 release page covers the phase rhythm that the next patch has to fit into.

Sources

This page is rebuilt each time a maintenance notice is published. The last version covered is 3.8, live on November 12, 2026.