Yoshi and the Mysterious Book has a soft-lock, and Nintendo needs to move fast

A progression bug is annoying when it costs you ten minutes. It becomes a real problem when it turns a family-facing Nintendo release into a soft-lock lottery built around a sequence no normal player would think to avoid. That is the situation with Yoshi and the Mysterious Book, where Nintendo has now confirmed a game-breaking issue that can trap players in the Index and stop progress entirely.

The company says the bug can occur if players start the Bird of Paradise investigation before hearing Fukashigi’s explanation of the “Index,” complete that investigation without making a major discovery, and then later trigger the Index explanation. Once those conditions line up, some players can end up unable to exit the Index page. Translation: your save is effectively stuck until Nintendo patches it.

This is not a balance issue or a quirky edge case

Nintendo has framed the problem clearly enough: this is a progression-blocking bug, not a cosmetic hiccup and not the usual “rare issue under certain conditions” wording that publishers like to hide behind. That matters, because the practical effect is severe. If you hit this state, the game stops being playable in the way that matters most. Progression locks are among the few bugs that instantly override almost every other conversation around a game, whether that conversation is about charm, level design, or performance.

The trigger sequence is also exactly the kind of thing QA teams hate: specific, multi-step, and dependent on players approaching systems out of expected order. According to Nintendo’s explanation, the problem revolves around the intersection of the Bewilder Bird or Bird of Paradise research branch and the Mr. E’s Index tutorial. In other words, this is not “the game crashes when you press jump.” It is a state-management failure. One tutorial flag appears to assume another piece of progress happened in a strict order, and when the player slips outside that lane, the game can trap itself.

That sounds technical because it is technical. But for players, the takeaway is simple: a game built around discovery and experimentation has a bug caused by discovery and experimentation happening in the “wrong” order. That is the uncomfortable observation Nintendo would rather not headline, because it cuts directly against the design pitch.

The awkward part is how easy this is to stumble into by playing naturally

On paper, the sequence sounds narrow. In practice, it is the kind of narrow bug players can still hit by accident because the game’s structure seems to encourage poking at systems before every tutorial box has fired. If you give players investigations, creature-based experiments, and a mystery-book framing device, some of them will absolutely wander off and touch the interesting thing first. That is not weird behavior. That is the intended fantasy.

This is where Nintendo’s track record matters. The company usually earns the benefit of the doubt on usability and tutorial flow in first-party-style projects because its best games are built to survive player curiosity. They bend, then recover. When a Nintendo-published or Nintendo-associated release instead breaks because a player explored a system before the script expected them to, that stands out.

It also lands at a bad time for this particular game. Early critical reaction, including background coverage from outlets like IGN, has already suggested Yoshi and the Mysterious Book is charming but uneven, with inventive ideas that do not always hold up across the full runtime. A progression lock does not just add one more complaint to that pile. It hardens the perception that the game’s systems were not fully stress-tested once players started pushing at the edges.

Nintendo did the right first step, but the missing detail is the one players care about

Credit where it is due: Nintendo acknowledged the bug publicly instead of pretending forums would sort it out. That is the minimum, but minimum is still better than silence. The company has said a patch is in development and apologized for the inconvenience. Some reports also indicate the fix is meant not only to prevent the bug going forward, but to restore progress for affected players. If that holds, it is the best-case outcome.

The problem is the obvious one: there is no ETA. And for progression bugs, “a patch is coming” without a date is only half an answer. Players who are already stuck need to know whether they should wait, restart, or shelve the game. If the practical workaround is “start a new save and carefully avoid the trigger conditions,” that should be stated plainly. If Nintendo expects the patch soon enough that restarting would be pointless, that matters too.

The question I would put to Nintendo PR is straightforward: can the incoming update reliably free already-soft-locked saves, or is this primarily a preventative fix? That distinction is the whole story for affected players, and companies often blur it because “fix incoming” sounds cleaner than “future players will be safe, current players might be out of luck.”

What players should do right now

Until the patch arrives, the safest move is to avoid the exact sequence Nintendo described. If the game prompts you to view the Index explanation, do it immediately rather than putting it off. More specifically, do not begin the Bird of Paradise investigation before that explanation, and do not assume the game will gracefully handle backtracking into the tutorial state later.

• If you have not reached the relevant section yet, take the Index tutorial as soon as it appears.
• If you are near the Bewilder Bird or Bird of Paradise investigation, avoid testing the sequence Nintendo flagged.
• If you are already trapped in the Index, there is currently no confirmed player-side fix from Nintendo beyond waiting for the patch.
• If customer support options are available in your region, report the issue anyway. More case data usually helps accelerate triage and patch priority.

None of that is ideal. Players should not need a pre-flight checklist to avoid bricking progress in a Yoshi game. But here we are.

What to watch next

There are three things worth watching, and they will tell us whether this is a contained stumble or a larger warning sign.

• First, Nintendo’s patch notes. If the fix explicitly says existing saves will be recovered, confidence goes up immediately.
• Second, timing. A fast patch suggests Nintendo had a narrow repro case and a clean solution. A long delay suggests the progression logic is messier than the public wording implies.
• Third, whether additional edge-case bugs surface around the same tutorial and research systems. One state bug can be bad luck. Multiple bugs in the same flow usually means the structure is brittle.

For now, the story is not that Nintendo found a small issue and promised to look into it. The story is that a game about playful discovery currently punishes players for engaging with its systems out of sequence, and Nintendo has not yet said when that stops being true.