I dropped into the Dam Battlegrounds and watched a player walk through a gate they shouldn’t have reached. My raid leader cursed, the mission failed, and we all stared at the same invisible wall. You probably slammed your controller on that exact moment.
I’ve been tracking the patch notes across Steam, Reddit threads, and the studio’s X posts so you don’t have to. The new hotfix for the Shrouded Sky update patches a handful of mission-breaking bugs, corrects exploit paths, and tightens some loot math. If you’ve been stuck on the final step of the Worth Your Salt quest or saw someone solo into the Dam Controlled Access Zone, this change matters.
At the Dam I watched a solo raider slip past a gate — What the access-zone exploit meant for raids
Observation: a solo player reached the Dam Controlled Access Zone that is supposed to be a four-player area and the screen went quiet. That breach broke encounter pacing and ruined objectives designed for squads. The studio pushed an urgent fix that closes the exploit, restores intended difficulty, and keeps squad mechanics intact for the Dam Battlegrounds map.
During a First Wave run I noticed fewer blueprints drop — Changes to loot and cache balance
Observation: on Hurricane-condition runs I opened caches expecting blueprints and walked away with materials instead. The hotfix slightly lowers rare blueprint drop rates while increasing high-tier material drops from First Wave Caches under the Hurricane map condition. This nudges resource flow toward crafting and material upgrades, shifting the economy for players who rely on blueprint farming.
- Resolved an exploit that allowed weapons to be stored in safe pockets without the Safekeeper Augment.
- Addressed an issue where the Snaphook could be placed in a safe pocket while actively in use.
- Slightly lowered rare blueprint drop rates and increased high-tier material drops in First Wave Caches (Hurricane map condition).
- Deployed an urgent fix for the glitch that allowed players to access the Dam Controlled Access Zone solo.
- Fixed intermittent frame rate drops caused by certain ARC assets.
- Fixed the final stage of “Worth Your Salt” so it completes even if another player in the raid already finished it.
In a match I watched the quest marker never clear — Why the Worth Your Salt bug was so maddening
Observation: my teammate had finished the quest earlier in the run and the objective never registered for anyone else. That scenario turned the final step into a brick wall, one that dozens of players reported on Discord and Reddit. The hotfix patches the completion logic so your run counts even when someone else already cleared the objective — the quest system was a locked door that the patch finally turned a key on.
Why couldn’t players complete the “Worth Your Salt” quest?
Short answer: a race condition in the quest completion checks meant that if a different player triggered the objective first, others could be left in a stuck state. The studio fixed the server-side logic; you should now get credit when the last step resolves on your client.
On stream my framerate dipped during an attack wave — The technical and client-side fixes
Observation: frame drops hit during certain ARC-heavy encounters and your stream chat lit up. The hotfix includes a fix for intermittent frame rate drops tied to specific ARC assets. That’s good news for players running Nvidia or AMD GPUs while streaming on Twitch or capturing via OBS, and it’s something content creators on Steam and YouTube will notice immediately.
How do I know if the hotfix is live on my platform?
Check the platform client: Steam will show a small update flag, consoles will download the patch via their normal system updates, and the studio confirmed deployment on X. You can also watch the game’s official Discord or r/ArcRaiders on Reddit for player confirmation and early reports.
Other notes: the Snaphook safe-pocket placement and Safekeeper augment exploits were closed, which reduces item-safeguarding workarounds. If you’re a streamer or competitive player, expect fewer odd edge cases during runs. The patch acts as a bandage over a gash in matchmaking and mission logic — serviceable, but you’ll still want subsequent fixes for polish.
I’ll keep scanning patch threads on Steam and the community channels for follow-ups; you should test your own workflows and post reproduction notes if something still slips through. Has this hotfix fixed the runs that used to break, or did it only mask the symptoms—what have your squads noticed?