Why Hollow Knight: Silksong Took Seven Years — The Real Story Behind the Wait

Seven Years Later, Silksong Is Real – Here’s What Actually Happened

Hollow Knight: Silksong finally launched on September 4, 2025, ending the most memed delay in indie gaming. Bloomberg’s Jason Schreier reports the long wait was about craftsmanship from a tiny team, not production hell. That caught my attention because, in an industry obsessed with quarterly roadmaps, Team Cherry basically said: we’ll ship it when it’s worthy. As someone who lived inside Godhome and spent far too many nights mapping out Deepnest, I wanted to know if the wait was for the right reasons.

Key Takeaways

• Silksong grew from a planned DLC into a full sequel, expanding the scope and the calendar.
• Team Cherry’s small crew chose iteration and polish over speed, avoiding outsourcing armies.
• A deliberate communication blackout preserved surprises but frayed community patience.
• If the level design and systems match the ambition, the wait buys us depth-not bloat.

Breaking Down the Delay: From DLC to “This Got Big”

Silksong didn’t start life as a sequel. It was a DLC idea that ballooned. That shift matters: a feature set built for an add-on suddenly had to carry an entire game. Instead of clever detours, you need a world that stands on its own, economies that escalate, and a quest structure that sustains dozens of hours. That’s where calendars explode. By all accounts, Team Cherry decided to expand the map, deepen quest systems, and make Hornet’s moveset the backbone of traversal and combat-work that demands bespoke enemy behaviors and encounter design, not just reskins.

The Small-Team Reality: Craft Takes Time

Team Cherry isn’t a 300-person studio with parallel pipelines. It’s a handful of developers wearing multiple hats. Animation, encounter scripting, world layout, music integration—when a team like this changes a traversal ability (and Hornet’s kit is faster and more vertical than Knight’s), they’re not just tuning numbers; they’re rebuilding rooms, reconsidering enemy telegraphs, and rebalancing resources. Multiply that by bosses and biomes and you get years of iteration. The Bloomberg story frames it simply: they wanted to make something special and wouldn’t rush.

As Ari Gibson put it in the interview, “We had fun. This project is primarily a vehicle for our creativity. It’s enjoyable to create fun things.” That line will either melt your heart or make you roll your eyes depending on how long you’ve had “Silksong when?” in your vocabulary. My read: it’s the honest reason a polished indie arrives late—because when you own your IP, you can take the time.

Silence as Strategy: Smart or Self-Inflicted Wound?

Team Cherry mostly went radio silent for long stretches. From a dev standpoint, that’s a shield: fewer promises, fewer walking-back moments, and no trailer cadence to distract them. From the player side, it stings. Expectations swell, rumors spiral, and the meme machine eats your messaging. Personally, I’d rather have fewer updates than a string of slippery dates—but there’s a middle ground. A yearly check-in saying “still heads down, still expanding” would have cooled the temperature without giving the game away.

Does the Wait Pay Off for Players?

Silksong’s promise lives or dies on feel. Hornet’s speed needs pristine enemy telegraphs and levels tuned for momentum—think chase lines, silk-powered recoveries, and room geometry that encourages flow instead of friction. If Team Cherry nailed that, the expanded questing could give the world long-tail texture rather than checklist bloat. If they missed, we’ll feel it the second a fast kit collides with cramped arenas or muddy tells.

The Metroidvania bar rose while Silksong was cooking. Metroid Dread proved big-budget precision is back. Blasphemous 2 tightened combat without losing identity. Prince of Persia: The Lost Crown flexed modern movement in layered maps. And Animal Well reminded everyone that secrets can be the whole point. Silksong has to stand out with encounter design and world coherence, not just difficulty or size. Team Cherry did it once; the question is whether the jump from DLC-scope to “whole new kingdom” kept their trademark clarity intact.

Indie Time Is Real Time

For perspective, Cuphead took about seven years. Owlboy took nearly a decade. Small teams with custom art and bespoke systems move slower—and usually ship once. There’s no sequel factory, just people obsessing over frame timings and room edges. The difference with Silksong is that it lived under a spotlight from day one. Hype compresses patience. But craft doesn’t compress. If nothing else, this launch is a quiet win for “when it’s ready” in a market that often punishes that philosophy.

What I’ll Be Watching Post-Launch

First: performance and input latency on each platform—Hornet’s speed won’t forgive stutter. Second: quest structure. Are objectives guiding exploration or dragging us away from curiosity-driven routes? Third: balance. Hollow Knight’s best moments came from tough but fair bosses that taught through motion, not text. If Silksong keeps that ethos, the seven-year runway translates into mastery, not feature creep. If not, expect the community to mod and map their own fixes on PC while patches roll in.

TL;DR

Silksong took seven years because a small team chose scope and polish over deadlines—not because the project crashed and burned. The gamble only pays off if Hornet’s faster kit, bigger world, and quest systems feel cohesive on day one. We finally get to find out.