In 2026, the first official Hollow Knight: Silksong update reads less like a routine patch note and more like a snapshot of Team Cherry responding to the loudest launch-week conversations. When Silksong arrived on September 4, 2025, players celebrated the long-awaited sequel, then quickly began debating its difficulty. Bosses hitting for double damage, Hornet’s generous hitbox, and the sharpness of early encounters became recurring topics. Team Cherry’s answer was not a dramatic overhaul. It was a focused first update that fixed bugs, softened two early bosses, and signaled that more work was coming.

What the first Silksong patch actually changed

The short version is simple: Team Cherry opened the first update as a public-beta branch on Steam and GOG, then aimed for a full release on PlayStation, Xbox, Nintendo Switch, and PC by the middle of the following week. The studio called that timing an estimate, leaving room for slippage if issues appeared. For players who had spent years waiting, the patch mattered because it addressed problems that could stop a run outright, not just cosmetic annoyances.

The balance adjustments were deliberately modest. Team Cherry described a slight difficulty reduction for two early-game bosses, Moorwing and Sister Splinter. Sandcarvers were tuned to deal less damage. The pea pod collider received a slight increase in scale. Mid-game Bellway and Bell Bench prices came down a little, while rosary rewards went up slightly for relics and psalm cylinders. Courier deliveries also became more rewarding. None of these changes rewrote the game, but together they made the opening hours less punishing and the economy a bit friendlier.

The bug-fix list was just as important. Players could previously remain cloakless after the Slab escape sequence. The wish Infestation Operation often could not be completed during the late game. Beast in the Bells could become incompletable when the Bell Beast was summoned at the Bilewater Bellway during the late game. Team Cherry also fixed getting stuck floating after down-bouncing on certain projectiles, courier deliveries sometimes being inaccessible in Act 3, craft bind behaving incorrectly in memories, and a Lace tool deflect soft-lock at the start of the Deep Docks battle. Silk Snippers in the Chapel of the Reaper could sometimes get stuck out of bounds. Claw Mirrors could leave Hornet inverted if damage landed during a specific binding moment. Snitch Pick was not giving rosaries and shell shards as intended. The update also removed the float override input of down plus jump after the player has the Faydown Cloak, and it included various additional fixes and tweaks.

Why the early-game difficulty debate would not fade

Was Silksong too hard at launch? That question followed the sequel from its first week. Some players pointed to double damage from bosses, Hornet’s large hitbox, and the general speed of encounters. Others argued that Hornet is much quicker than the Knight from the original Hollow Knight, and that mobility should balance the higher threat level. Team Cherry did not settle that debate with the first update. Instead, the studio made a careful concession: two early bosses became slightly easier, and Sandcarvers became less dangerous. The patch did not gut the challenge. It nudged the opening so more players could find their footing.

That restraint is worth noting. A blunt difficulty pass could have flattened the sequel’s identity. Team Cherry chose small adjustments, the kind that help players learn the rhythm without removing the sting. For a game built on precision, that distinction matters.

The translation problem was bigger than bugs

The first patch also arrived during a larger conversation about localization. Reviews for Silksong were largely very positive or overwhelmingly positive, but Japanese and Simplified Chinese reviews were mixed. In Simplified Chinese, only 40 percent of roughly 36,000 reviews were positive at the time. That is a striking gap for a sequel receiving so much praise elsewhere. Team Cherry said it was working on rectifying the problem, with improvements expected in the coming weeks.

For a text-heavy adventure, translation is not a side issue. Item names, wish descriptions, and dialogue all shape how players understand the world. The first update did not solve that overnight, but it put the issue on the record. In 2026, the patch is remembered as much for that localization promise as for Moorwing and Sister Splinter.

A beta branch, a full rollout, and more fixes to come

Team Cherry also said further fixes were in the works. That note mattered because patch notes rarely cover every reported problem. Players dealing with an unlisted issue could reasonably assume it was being investigated for the second update. The first patch was a starting point, not a final statement. The beta branch on Steam and GOG gave eager players an early look, while console and storefront releases followed the studio’s estimated schedule.

Looking back from 2026, the first Silksong update set a useful tone. It made the early game more welcoming without erasing the challenge. It cleaned up soft-locks and progression blockers. It acknowledged the localization problem instead of ignoring it. For a sequel that spent years in anticipation, that first patch was a reminder that post-launch support is part of the experience. 🎮

For players who set Silksong aside and are now considering a return, timing can matter as much as patch notes. Watching for discounts across storefronts makes it easier to jump back in without paying full price, especially when DLC or related releases enter the mix.

That is where a deal tracker can help. DealNest game deals gathers current offers in one place, giving you a straightforward way to check prices before committing to a purchase or recommending the game to someone else.