Gearbox reveals its Risk of Rain 2 Rescue Plan two months after the Seekers of the Storm expansion disaster, and players seem to be pretty excited.

Gearbox Software, less than two months after the release of Seekers of the Storm - its first expansion to Risk of Rain 2 - has revealed its plans for the future of the expansion. It hopes that "Seekers of the Storm will become something that the community can celebrate for years to come."

Gearbox purchased the Risk of Rain franchise in 2022 and promised to provide players with "world-class" content, as well as a "bright future for this genre leading franchise." We noted that many fans were not convinced. It turns out, they were right: Seekers of the Storm was released in 2024 with a terrible state. This caused problems for everyone, including those who didn't purchase the expansion.

Gearbox has released a few small updates since then, but we now have a fuller look at their cleanup plan. This includes "significant" changes to Seekers of the Storm. Gearbox has said that it is "exploring" new updates, so I assume some of them aren't set in stone yet. However, the general strategy will unfold in three phases, focusing on Items, Elites, False son boss fight and Survivors.

The project is going to be huge: all but one of the items added to Seekers of the Storm will be completely redesigned in order to make them more "transformational," and to better fit "existing build synergies." And the False son fight will be redesigned and balanced to make it "more fair and clear." All three survivors of the game will receive "large improvements," but Chef is getting a special focus. He's being rebuilt, buffed and made more powerful.

Gearbox has not revealed a specific time frame, but said that the changes would be implemented over the next few weeks. Gearbox wrote: "This is an enormous undertaking, but the team is excited." "We would also like to thank everyone who has given us the time to create a holistic plan. We know you're eagerly awaiting to see what lies ahead, and we can't help but be excited for you to jump right in.

It's understandable that there is some skepticism about the Steam roadmap announcement. This was an unforced error, and it was made worse by the fact that so many people predicted it two years ahead. There are also a lot of responses expressing gratitude to Gearbox for its commitment to fix what it broke and for clearly communicating their intent to players. There's no consensus, but there is a legitimate, widespread hope that Gearbox can, eventually, fix the problem.

Gearbox has released a new patch to fix bugs in Risk of Rain 2 for PC. Console updates are expected over the next week. Below are the full patch notes.

V1.3.5 Notes:

• Resolved an issue reported by a player that caused the spawn rate for elites to be too high after Stage 2.
• The Mul-T Sentry Skin has been tweaked in order to remove a small spike that was reported by some players.
• The reported issue of the Voidling not appearing when the second phase was started has been resolved.
• False Son might have difficulty using his 'charged attack' if your attack rate became extremely high. This issue has been resolved. You can now print syringes as you please.
• Some players who were connected reported that Seeker’s Spirit Punch could collide twice with an enemy and deal double the damage. This has been fixed.
• As a connected customer, players reported that The False son's Boss battle would sometimes not display certain animations. He is now using his abilities correctly.
• On a certain version, players reported that a mysterious floating branch would appear. The tree has now been returned to its original location.
• Players reported that lightning on Prime Meridian only targeted the Host during multiplayer sessions. Lightning will now target everyone equally.
• The platforms for The False Son’s arena on Prime Meridian did not always change for clients as they moved between phases. They will now appear/disappear the same as they do to the host.
• Resolved an issue reported by players that sometimes prevented them from properly spawning when entering cross-play sessions.
• Xbox glyphs are displayed instead for players who use PlayStation controllers. The correct glyphs are now displayed.
• Players who were connected reported that The False Son’s large boss health bar sometimes did not reappear when changing phases. Now, it will appear for all players.
• Resolved a reported problem with the Prismatic Trail leaderboard not displaying times.
• The new Aphelian Bulwark Variant Aphelian Bulwark Armor Variant has been reported by players to have a mysterious Xi Construct. This monster has been removed from the pool of monsters.
• The affliction stacks Tonic gave you displayed a placeholder description.
• Prime Meridian event achievement no longer unlocks after killing only one of the False son bosses when using Artifact of Swarms to fight the False-Son Boss.
• We received reports from players who tried to join lobbies that it would sometimes not allow them to do so and not explain why. A problem has been resolved which prevented certain error messages from appearing when joining lobbies. One of the most common was that a user with crossplay enabled would not receive a message if they tried to join a lobby without crossplay.
• Resolved a bug that could sometimes trap the player outside of The False Son boss room after being resurrected.
• Occasionally, when playing as Mul T and using the Sentry skin the visual effect of being frozen would not be visible. Mul-T can now be turned into an ice block.
• Players reported that applying bleed to Noxious Thorns caused monsters to turn on each other, and ignore the player. This issue has been resolved.
• Noxious Thorn was unable to correctly apply +1 stack of another active debuff. It sometimes applied only its bleed stack.
• The issue with using Sojourn or Eccentric Vase or Volcanic Egg that prevented you from viewing the False son fight or teleporting to the platform has been resolved.
• The Wandering Vagrant’s homing orbs can sometimes become invincible, according to players. This issue should be addressed.