Why Hidetaka Miyazaki Dares to Wait Another Year: The Duskbloods Delayed to 2027 and the So-Called Proactive Delay#

Chasun | October 31, 2026

On October 29, this Japanese developer posted a notice of under two hundred characters on its official social account: the release window for The Duskbloods, an exclusive for Nintendo’s next-generation console (Switch 2), has moved from 2026 to 2027, with no specific month or day given, only the year confirmed (publisher announcement). At the same time, Nintendo’s official German, French and Italian accounts relayed it in sync, describing the new 2027 window as being “to deliver the best possible gameplay experience” (relayed from the publisher announcement).

What is really worth writing about is not “another delay,” but how specific the reason in this notice is. The official line was not “we need more time to polish”; it named what is going to change: based on the feedback from all users received in the August network test, in order to realize this game’s concept at a higher level — letting players have fun not only through direct combat but also through a variety of movement and rich strategy — it has decided to set aside a stretch of time devoted specifically to final adjustments to the game’s rules and balance (publisher announcement). In that sentence, “rules” and “balance” are two verifiable words: they correspond to numbers, mechanics and match structure, not to levels or assets that have not yet been finished.

That is the dividing line this article wants to draw. There are two kinds of delay: one is not being finished, pushed along by the schedule, where the reason can only stop at “it is not ready yet”; the other asks “is it fun?” before it is finished, and the reason can land on the specific things to be changed. The former is passive, the latter proactive. Every piece of public information about this delay — the August test, the login failure in the first session, the character power gaps repeatedly flagged in previews, the phrase “not only through direct combat” in the notice — falls on the latter side.

Of course, proactive versus passive is never a label that an official statement alone can establish; it needs an evidence chain. The order below is: first read the notice apart, then string together the causality between the August test and the October 29 notice, then give the classification framework and its limits, and finally tally the cost of this delay — including the gap in the console’s schedule, and the share that players themselves pay.

1. Reading the Announcement: Four Specific Items Hidden in the Official Wording#

Read those five rows together and the sharpest one is the second. The phrase “not only through direct combat” amounts to official admission: what was not fun in the network test was not the part where fighting happens, but the part outside it — whether movement matters, whether strategy has depth, whether players can win in their own way. For a game with eight players in a match that has to handle both opposition and the environment, this is exactly the hardest thing to patch in before launch: once the structure of a single match is set, post-release number tweaks can change strength, but they cannot change “what this match is actually about.”

The fourth row marks the point in time. What the official wording says is “final adjustment stage,” not “middle of development.” That means the extra year corresponds, on paper, to an extension of the finishing process rather than a teardown and rebuild — though the same caveat applies: this is the publisher’s own wording, outsiders cannot verify the actual internal completion state, and readers should treat it as an official account rather than a factual conclusion.

There are three easy traps when reading notices like this; let us clear them here first:

• Do not read a specific date into it. The notice only goes as far as the year 2027; any extrapolation about quarters or months is secondary processing, and this article does not do it.
• Do not read “final adjustment stage” as “almost done.” It describes a position in the process, not the remaining workload; there is no derivable relation between the two.
• Do not read it as “back to the drawing board.” What the official wording names is rules and balance, not content volume or technical architecture; calling this delay a rebuild goes beyond what the text of the notice can support.

2. The August Test: How Feedback Turned Into a Decision#

The problems exposed during the test are almost the same set as what the official side later said it would fix:

• The endgame deformed. Some hands-on previews noted that the final decisive battle arena turned into a chase in actual matches, with players repeatedly farming jumps, dashes and ranged attacks (media hands-on preview account). This echoes the official “not only through direct combat” line — what got farmed away was precisely movement and strategy.

• Clear character power gaps. The same previews considered the sniper Laila the strongest playable character, while slow characters such as Zoc and Bloodhand Jane were clearly weak (media hands-on preview account). In a game built around preset characters rather than created ones, that gap directly decides whether the strategic space of a match holds up.

• The service side failed first. The login errors in the first session led the official side to end that session early and apologize (media reporting), meaning part of the first-hand data the test originally collected was discounted.

• An account overturned by itself. The parent company’s February financial report still listed the game as releasing within the year (media relay of the report, original not obtained), the September Nintendo Direct again announced no release date (media reporting), and only on October 29 did the official line formally change. This chain shows: the decision was not made on the day of the notice, it was a postponed announcement.

Two more details deserve separate mention. One is the applicant count: the producer says applications for this test exceeded those for the Elden Ring Nightreign test (producer statement), but no absolute figures exist in public information, so it can only prove “attention is higher than for the previous title,” and cannot be converted into any retention or approval metric. The other is the double impact of the first-session failure — it led the official side to apologize the same day and end that session early (media reporting), and it also means the “server load” test goal did not get complete data in the first session; only when later sessions were more stable did balance data collection truly begin. In other words, the output of this test did not arrive in one shot; it accumulated after the door was fixed.

From August 21 to October 29 there is a gap of a little over two months. That is enough time to turn test data into balance conclusions, and enough for a game already in its final adjustment stage to decide whether to move the whole window back — the causal chain the notice gives is complete: the test collected feedback, feedback pointed at rules and balance, rules and balance need time, so the date changed.

3. Proactive and Passive: A Dividing Line and Its Limits#

Check this delay against them one by one: the reason points at rules and balance; the preceding event is the August network test with explicit test goals; the announcement comes before the parent company’s earlier “within the year” account has expired; Nintendo’s three regional accounts and the developer are consistent; and the delivery expectation is given as 2027 — five out of five. That is the basis on which this article puts it on the proactive side, and this classification is itself media analysis, not an official characterization.

This dividing line also has a layer of historical depth worth mentioning. In the games industry, “delay” has long been treated as a negative signal, because most of the time it really does mean estimation error, scope running out of control or a technology debt explosion. But the act of delaying is itself neutral: it only moves the delivery point later, and what actually determines its nature is “what the freed-up time is used for.” When the reason can land on specific mechanics, a delay is in fact a quality decision; when the reason can only stop at adjectives, it is a schedule accident. Telling the two apart is not complicated — look at whether the officials dare to say what is being changed.

Pull the lens back a little and the industry’s narrative about delays has roughly gone through three kinds of writing, and this one belongs to the third:

• The first is the accident narrative. Not finished is not finished; the notice can only apologize, and players can only wait. The signature of this kind of delay is that the reason gets shorter and shorter.
• The second is the marketing narrative. The delay is packaged as “for something better,” but with no verifiable preceding event behind it; the reason gets longer and longer while the information content keeps dropping.
• The third is the engineering narrative. First a public round of data collection, then a notice naming what will be changed, with a verifiable time gap in between. The August test and the October notice here fall exactly into this square — and precisely because of that, the “proactive” label is not flattery, but a checkable classification (the classification in this paragraph is media analysis).

The limits must be written clearly: this dividing line is an external observation tool, not an internal fact. The official side says it will change rules and balance; we cannot verify whether this year’s actual workload matches that, nor can we rule out schedule factors existing at the same time. All that can be confirmed is the mutual corroboration between three things: the text of the notice, the test event, and the hands-on feedback.

4. Where the Game Sits: Not a Title You Can Just Move Around#

Hidetaka Miyazaki has previously said he hopes this game’s design will deliver “unexpected drama” (media reporting). That line reads differently next to this delay: drama depends on there being enough variables, and on each variable mattering — which is exactly the part where balance is hardest and most easily sacrificed to “ship first, fix later.” When the game was revealed, its multiplayer focus raised concern among some fans, and Miyazaki responded that the studio will still actively develop games centered on the single-player experience that embrace its more traditional style (media reporting); this notice shows that, on this title at least, the team chose to get the rules and balance of multiplayer matches right first.

Following that thread, the studio’s two previous titles remain the most fitting entry points for comparison: for the console-exclusive lineage see the Bloodborne section page, and for the most recent multiplayer attempt see the Elden Ring Nightreign section page.

5. Mechanics Breakdown: Why Rules and Balance Are the Hardest to Fix After Launch#

To judge whether this round of “final adjustments to rules and balance” is worth a year, you first have to see what this game hands over to its rules. The match structure shown in the network test (test mechanics compiled by media) can be split into these layers:

Sort those six layers by repair cost and you can see why the official side chose to delay rather than ship:

• The numbers layer is cheapest. Damage, cooldowns, movement speed and the like can keep being tuned after launch, and players are used to season-style power rotation.
• The rules layer is next. Change the elimination line, scoring weights or phase length and the match understanding players have already built is overturned wholesale; it is a “change once and reteach everything” case.
• The structure layer is most expensive. Player count, phase count and decisive format decide “what this match is.” Once that is admitted to be a design error after launch, the only fix is a rebuild, and rebuilding costs far more than moving the launch date back a year.

The official line about “not only through direct combat, but also through a variety of movement and rich strategy” lands right between the second and third layers: what was named for repair is not the damage of some weapon, but “how else can you win besides fighting.” That is exactly the interval patches are worst at and delays are best at.

6. The Cost: One Less Card for the Console, One More Year for Players#

The platform row has to be put absolutely clearly: “this game is one of the few strong first-party-tier exclusives on Nintendo’s new console, and pushing it to 2027 will leave a gap in the console’s big-title schedule next year” is a media analysis judgment, not an official statement from Nintendo or the developer. Only two verified facts support it — that the game is published by Nintendo and exclusive to that console (publisher announcement), and that the parent company’s financial report previously listed it within 2026 (media relay). Getting from those two to a “schedule gap” crosses into analysis rather than fact, and readers should keep their own discount on it.

The player side’s bill is more concrete, and more easily overlooked:

• Time cost is non-refundable. Counting from the April 2025 reveal, the wait has been stretched to span at least two calendar years, and the new window is still only a year, with no month or day.
• Test memory decays. Much of the match understanding built up by the players who joined the August test will need rebuilding when things reopen a year later — for a game that stresses movement and strategic depth, that is itself a hidden cost.
• Purchase resolve slips a notch. For some users, this exclusive is part of the reason to buy the console; moving the window back a year also moves back the day that reason pays off.
• Expectation gets re-priced repeatedly. Every time the official side announces a new window, players have to redo their mental pricing; this is also why “only a year” burns trust more easily than “a clear quarter.”
• Sunk feeling for test participants. The players who submitted feedback in August originally expected their views to be turned into the retail version within months; looking back a year later, whether the issues they raised were really adopted can only be proven by the finished product itself.
• Contrast effect. Two other titles sat on the same day in “just shipped” and “about to ship” states, and the gap in how waiting feels is amplified — which is why this notice is discussed in industry context rather than in isolation.

Of those six, the first three are hard costs and the last three soft costs. The publisher’s apology and thanks for patience (publisher announcement) correspond precisely to the latter three: they show up in no line of any financial report, yet they decide whether players are still willing to believe next time a date is announced.

7. Same Day, Three Finishing Paces#

On the same day, these three are exactly three completely different finishing postures: one hands the product to players first and accepts that the first batch of negative reviews clusters at the “can I even play” layer; one is a ten-year run reaching its station, where the hardest process becomes not changing anything more; the third brakes voluntarily in the final stretch. There is no ranking among them, only trade-offs — but set side by side, the third kind has become quite rare this year.

The point lands here: in 2026, with the games industry ever more mature, selling well and playing great have never been two things that automatically draw an equals sign. The first-day peak can be very high and the review scores can be very pretty, while the most-cited negative reviews all happen before the game is even opened; conversely, an unshipped game can push its whole window back a year for a line as vague-sounding as “movement and strategy should be fun too.” The former’s cost is paid by players first, the latter’s by the publisher first. A delay is one of the few decisions still daring to make way for the latter — and whether that daring holds up depends on whether the match delivered a year from now is really more worth playing than the one in the August test.

Sources#

• FromSoftware official social account notice (October 29, 2026): release window moved to 2027, final adjustment stage, final adjustments to rules and balance; publisher announcement in nature.
• Polygon (overseas games media): full English text of the official statement and the wording of the second post, including the line “not only through direct combat, but also through a variety of movement and rich strategy”; media reporting in nature.
• Fextralife (fan wiki site): network test details, first-session login failure, applicant count exceeding the previous title’s test, character power in hands-on feedback; media reporting in nature.
• Tencent News: August 21 test timing and official test goals (server load, connection stability, balance data); media reporting in nature.
• Gamersky and Ali213: Chinese wording of the official notice and the preset character system account; media reporting in nature, to be distinguished from the character count actually playable in the test.
• Overseas games media (contemporaneous reporting on both Chinese and English sites): the game’s absence from the September Nintendo Direct and outside expectations of a delay starting from there; media reporting in nature.
• UK games magazine November issue cover story (relayed by multiple overseas outlets): the “already good” and “letting go” lines used in the same-day comparison; media reporting in nature.
• First-day concurrent peak read by a third-party data site: 723,876 for Phantom Blade Zero on October 29; third-party reading in nature, used for the same-day comparison.
• This writing also used WebSearch to recheck public reporting around October 30, and found no official announcement of a new specific release date.