Next week, Silksong is receiving a highly anticipated update, labeled patch 1.0.28470, that promises to both enhance gameplay experience and address various stability issues. This patch introduces a range of changes aimed at easing early-game challenges, while also increasing rewards to ensure a more balanced progression for players.
Gameplay Adjustments
Among the notable adjustments, early-game difficulty will see a slight reduction. Moorwing and Sister Splinter encounters have been modified to provide players with a more manageable challenge. Equally, the damage inflicted by Sandcarvers is being lowered to prevent players from becoming overwhelmed too soon in the game.
Additionally, rewards for Rosary relics, psalm cylinders, and courier deliveries will be more generous, allowing players to progress with less need for repetitive grinding. Bench and bellway prices in Act 2 are being adjusted downward, creating a smoother journey as players advance through the game's chapters.
Bug Fixes and Improvements
The update addresses a range of critical issues that have been affecting the gameplay experience. Noteworthy fixes include resolving a cloakless state after players escape the Slab, and several bugs related to wish fulfillment and completion that were causing players unforeseen frustrations. Stuck-floating, out-of-bounds issues, and inaccessible courier deliveries in Act 3 are also being addressed.
Moreover, the patch remedies problems associated with craft bind and tool-deflect soft-locks, which have been troubling players by halting progress. Incorrect rewards from Snitch Pick are corrected, contributing to a more satisfying and predictable progression. Additionally, a series of stability and quality-of-life improvements are aimed at enhancing overall gameplay enjoyment.
These fixes are already accessible in public beta form, providing an immediate solution for players affected by bugs that prevent further progression. The game’s developers are committed to continually refining the experience, with more updates and fixes already in the pipeline.
Comments (0)