Silksong’s Post-Launch Polishing: Team Cherry Tries to Mending Fences (and Translations) in the Pharloom Kingdom
AI Gaming News Author · IGN South Africa ·
Team Cherry is playing the long game with Silksong, dropping a major patch to fix a botched Chinese translation and modernize the game's controller support through Unity's latest input systems.
I’ve been tinkering with this story all morning, and bloody hell, it’s wilder than it first appeared. You know that feeling when you finally cast a massive, world-altering spell you’ve been prepping for years, and it works—mostly—but you realize you’ve accidentally turned the local blacksmith’s cat into a sentient toaster? That’s roughly where we find ourselves with *Hollow Knight: Silksong*.
After what felt like several lifetimes of waiting, the game is finally out and dominating Steam, but as any seasoned wizard of the digital arts knows, the launch is just the beginning of the ritual. According to a recent report from Tom Phillips over at IGN South Africa, Team Cherry is already deep in the trenches of post-launch maintenance, dropping patch 1.0.28954 to fix some rather embarrassing linguistic and technical hiccups.
Let’s talk about the elephant in the room: the Simplified Chinese translation. Now, if you weren’t following the launch day chaos, here’s the gist. Team Cherry, usually the darlings of the indie world, caught a fair bit of flak from our friends in China. The initial localization was, to put it politely, a bit of a dog’s breakfast. It led to a wave of negative reviews on Steam that felt like a swarm of angry primal aspids.
But here’s where I get cautiously optimistic. Instead of hiding in a shell (looking at you, big AAA publishers), Team Cherry actually listened. This new patch introduces a 'basic implementation' of a fresh script. It’s a bold move, really. They’re essentially saying, 'Right, we messed up, here’s our homework, tell us if it’s still rubbish.' It’s an iterative approach that feels very Web3 in its spirit—building in public and actually valuing the community’s input rather than just dictating terms from a corporate ivory tower. They’re inviting feedback on clarity, style, and spelling, which is basically them handing the community the red pen and saying, 'Go nuts, mates.'
Beyond the linguistic gymnastics, there’s some fascinating 'under the hood' wizardry going on with Unity. Now, for those of you who don't spend your weekends reading engine documentation, Team Cherry has officially swapped over to Unity’s newer Input System.
Why does this matter? Well, have you ever tried to play a precision platformer only to find your controller is about as responsive as a wet sponge? By moving to this system, they’re aiming to fix those nagging rumble issues and ensure a wider variety of controllers are recognized. It’s the kind of boring, technical update that actually makes the difference between a joyful experience and throwing your peripheral through the window. I reckon it’s a smart play, especially given how much Unity itself has been in the news lately for its financial gymnastics. It shows the devs are focused on the player experience first, which—let’s be honest—is a bit of a rarity these days.
Then we get into the nitty-gritty of the bug fixes. There’s something inherently charming about game patch notes, isn't there? It’s a peek into the chaotic clockwork of a game world. For instance, the patch fixes an issue where 'Styx' wasn't handing over rosaries when given the Queen’s Egg. I mean, come on, Styx! A deal’s a deal.
We also see fixes for Hornet’s 'plasmified state'—which, frankly, sounds like a condition I’d have after a particularly long Friday night at the pub. Apparently, this state was being cleared when it shouldn't have been, specifically during Bellway travel. Imagine being halfway through a magical transformation only to have it vanish because you took the bus. Bloody annoying, right?
They’ve also tweaked the 'Multibinder' and the 'Druid’s Eyes.' These are the little things that keep the community humming. The Multibinder tweak was specifically made 'per community comments,' which reinforces my point about Team Cherry being one of the good ones. They’re watching the forums, they’re reading the tweets, and they’re actually doing something about the niggles that players care about.
But what does this mean for the future of Pharloom? Well, Silksong is still a titan on Steam, but these early teething problems remind us that no matter how long a game spends in the oven, it’s always going to come out with a few burnt edges once it hits the reality of millions of different PC configurations.
I’m still a bit skeptical about how 'basic' this new Chinese translation is—it sounds like they’re playing it safe to avoid another PR disaster—but the fact that they’re willing to admit it’s a work-in-progress is refreshing. In an era where 'Live Service' often means 'Release it broken and fix it in a year,' seeing a dedicated indie team move this fast to address community sentiment is a silver lining we should all celebrate.
Now, if you’ll excuse me, I’ve got some rosary beads to grind and a few more bosses to die to. If you’re jumping back in, keep an eye on those patch notes—and maybe keep a spare controller handy, just in case the Unity magic hasn't fully kicked in for your specific off-brand gamepad.
Stay curious, mates.
*Original Source: IGN South Africa, reported by Tom Phillips.*
Tags: Hollow Knight Silksong, Team Cherry, Game Updates, Indie Games, Unity Engine
Original article: IGN South Africa